5 ms·
> It's not that simple, some costs on AWS can be high and some tasks don't need the availability/reliability guarantees AWS provides. So even for small startups
by ldoughty 4y ago
> It's not that simple, some costs on AWS can be high and some tasks don't need the availability/reliability guarantees AWS provides. So even for small startups sometimes having own hardware can be a good cost saver, through with some risk attached to it
I agree. I'd like to add that AWS's value add can be the lack of need to understand the product configuration, just the SDK. Your start up already has developers that can read SDKs, you might not have someone on your staff that can set up an elasicsearch, redis, or other service.
When you grow enough that the fine tuning of such services might matter, you likely can hire the right people to run those in house.
I've been on a team with ~6 DevOps members for 5 years, and it's been very helpful to be able to pick up and drop services as we evolve.
- TimPC 4y agoI think it depends. My best friend works at a company that took four years to architect and build V1 of its product on prem. They had to build a lot of things by hand that are standard components in the cloud. They architected and built V2 on AWS is a single year. The higher cost is considered small by them compared to three additional years of waiting for a system to offer key features that upsell customers.