21–30 of 100 posts
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 read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
My last month's AWS bill (not in the free tier anymore) was only $2.23. For the runner that runs arbitrary shell commands I used to run a t2.micro in AWS but when the free tier expired I moved that over to gcp and I'm burning through their credits. I'm also using gitlab ci/cd to periodically renew the docker instance that runs shell commands.
It only works because there isn't much traffic obviously, and api requests are not made on every page load.
I read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
Yup. That would work, but it takes out a couple of things from the original requirements I had: 1. scalability It should be able to stretch especially for bursty traffic situation. 2. I should not have to pay if the app or service is not being used.
I read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
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.
- 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 wonder why people use AWS/GCP when the other providers are so much cheaper. How do Linode/DO offer such good prices? Would they kick me off if I actually maximized the server capacity they offer, like a shared cPanel host would do, back in the day?
I read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
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.
I read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
A single downtime event on a single host will likely have costs that can never be actuarially recovered from, in this head to head. Pay the $15 extra bucks.
I read this, and I think: wow, that's extraordinarily expensive. The stack he designs is $20/mo for 1,000 user sessions/day. Back in the days of cPanel/LAMP shared hosting, you'd have similar capability for $5/mo.
Yeah $5 for a single point of failure in one data center of possibly questionable quality. Versus 20 a month for an app spread across availability zones for the all-in price, resilient to failure on single machines, etc. A single downtime event on a single host will likely have costs that can never be actuarially recovered from, in this head to head. Pay the $15 extra bucks.
I think AWS would do well to expand massively its free tier. Talented startups in my world are starting to look askance at AWS fees.
Is it generally reliable asking Amazon support what capacity you need for a particular use case, so you're not buying more than needed? e.g. a service that might be used once per day for a minute, and another day it might get used a dozen times for maybe an hour, and only during fixed business hours. And there are general purpose, compute optimized, storage optimized, etc. But what if the service is more network late…
I am on GCP but I usually request/allocate more and once in production for a few weeks, I can turn some things down and others up. That is if your product/setup is new and you aren't sure how everything will interact once live (in terms of perf). Otherwise, for Lambda there is on Github a repo with a script that will publish your code in every configuration possible, run stress tests, and only keep the most optimum (…
I've put together a demo over at libra-shop.org. It definitely still needs some work, but I think most of the important bits are all sorted out.
Of course, the biggest issue with using free tiers for your entire stack is that you have no guarantee that the services will be running forever. (eg. Netlify could stop providing a free AWS Lambda connection)