Title: I&#x27;m pretty comfortable with AWS from work experience, but I also recall the insane bills we paid. Of course, the place I worked at was&#x2F;is doing great so the insane bills aren&#x27;t a problem for them (when we&#x27;re talking billions in revenue, a few million per year on AWS is okay I guess). They also have many, many petabytes of data and millions of users, though I&#x27;d argue there is also a ton of over-engineering.<p>Now that I&#x27;m working on my own company, I&#x27;m curious about alternatives to AWS.<p>I&#x27;m keeping things simple, so I&#x27;ve got mostly Go services, pg + caching, and a svelte webapp. I deployed my Go services on a low-ish end bare metal provider, and for now it is fine. Deployments are triggered via scripts, and so far so good. Is it sexy, using all the latest and greatest tech? No, its just simple shell scripts. But it works?<p>I also benchmarked each endpoint with tens of millions of records (not a whole lot but still) and I&#x27;m seeing a pretty good latency to throughput ratio. In fact, the performance is better than what we got during peak at work, and this setup is costing me tens of dollars a month.<p>That makes me think if I even ever really need AWS. If I ever need to do multi region, I can just spin up a new machine there. CDN covers all static content.<p>Am I wrong to think that I could probably scale like crazy and avoid AWS completely with my stack? Why should I pay hundreds&#x2F;thousands per month plus a premium for bandwidth? I&#x27;m also enjoying staying sane avoiding IAM.
Upvote: