|
|
|
|
|
by OutOfHere
761 days ago
|
|
For the 99% of use cases, you don't actually need AWS. I would stick to open source software/services, efficient code and algorithms in the fastest languages, cheaper smaller clouds, AI APIs, and even an in-house cluster for GPUs when needed. Keep iterating. If you're still running say Java with its enormous memory requirements, you are however stuck with the big clouds. |
|
For cloud-like provisioning experiences and paying by the hour you can use DigitalOcean, Vultr, or alternatives.
Deploying GPUs? Something like CoreWeave may be optimal.
Want inexpensive costs for dedicated hosts? Hetzner, OVH.
There are many, many advantages to using AWS but equally many alternatives that are viable and which aren’t “doing it yourself” in a hardware and network sense.
None of this is to say DIY is a terrible choice either and everyone’s got an opportunity to consider time (initial setup; ongoing maint), costs, and also expertise and ability to do a good job.