71–80 of 100 posts
Earlier quoted context omitted.
All of this work and complete dependency on third party services is worth it? Isn't much easier to create a lightweight app in say, Go and SQLite, and pay a so-low-to-be-insignificant monthly fee?
I wonder what amount of money would be sufficient to create the digital equivalent of a foundation to ensure the uptime of a website/project. It would be kinda cool to put away a few grand to ensure something stays up "forever".
Earlier quoted context omitted.
All of this work and complete dependency on third party services is worth it? Isn't much easier to create a lightweight app in say, Go and SQLite, and pay a so-low-to-be-insignificant monthly fee?
I wonder what amount of money would be sufficient to create the digital equivalent of a foundation to ensure the uptime of a website/project. It would be kinda cool to put away a few grand to ensure something stays up "forever".
In reality, it would probably be more effective to dedicate nearly $0 to infrastructure and $N,000.00 to an endowment for 1-3 hours of engineering time each year.
Figuring out how to host a static site for free and moving the site to that service requires almost no time for a competent engineer. But finding a solution that is guaranteed to exist in 100 years with zero human intervention would probably cost millions...
Earlier quoted context omitted.
With a basic DO droplet, you can still do that for $5/month, and hey, if it takes off your app won't depend on a bunch of expensive proprietary software. Also I'm guessing that if cost is a concern, denial of service is preferable to blowing the bank under unanticipated high loads. Maybe I need to drink more AWS/GCP kool-aid though and see the light.
Recently I've been fascinated at gap between server providers these days. It seems each provider is either: - Enterprise public cloud, AWS/GCP/Azure, expensive but scalable and enterprise friendly - Developer public cloud, Linode/DO, cheap and easy to use Although I say that AWS/GCP/etc are expensive, they obviously have negotiable prices for large customers. I doubt the smaller providers do that. But it makes me won…
This is a nice write up. My only concern is that these days we think that the alternative to free is $40 to hundreds of dollars a months for something decent. In the days of shared hosting, you could drop $3 to $5 to host your small website and expect your website to decently perform. But with your DO/Linode, you can expect excellent performance for the same price. Only last month my two $5 droplets handled 5 million…
Earlier quoted context omitted.
With a basic DO droplet, you can still do that for $5/month, and hey, if it takes off your app won't depend on a bunch of expensive proprietary software. Also I'm guessing that if cost is a concern, denial of service is preferable to blowing the bank under unanticipated high loads. Maybe I need to drink more AWS/GCP kool-aid though and see the light.
Recently I've been fascinated at gap between server providers these days. It seems each provider is either: - Enterprise public cloud, AWS/GCP/Azure, expensive but scalable and enterprise friendly - Developer public cloud, Linode/DO, cheap and easy to use Although I say that AWS/GCP/etc are expensive, they obviously have negotiable prices for large customers. I doubt the smaller providers do that. But it makes me won…
Here’s a boilerplate Go app that sets up this stack:
With all costs that goes into building a business (directly in $ or indirectly in hours) is it worth going down the path of saving money to this degree? Setup heroku in If $100/month breaks you, I think you’re in the wrong path anyways.
I find it even more efficient, since Go, AWS SAM and Lambda offers dev/build/prod simplicity that Heroku never figured out.
I open sourced and documented the stack that I use instead of Heroku here:
Earlier quoted context omitted.
I wonder what amount of money would be sufficient to create the digital equivalent of a foundation to ensure the uptime of a website/project. It would be kinda cool to put away a few grand to ensure something stays up "forever".
The price of forever ranges from a few hundred to millions depending on how resilient you want to be. In reality, it would probably be more effective to dedicate nearly $0 to infrastructure and $N,000.00 to an endowment for 1-3 hours of engineering time each year. Figuring out how to host a static site for free and moving the site to that service requires almost no time for a competent engineer. But finding a solutio…