3 ms·
> my belief is that the cloud _is_ cheaper than on prem but it is difficult to configure it to be so. It takes discrete effort in the core planning of your arc
by notyourwork 4y ago
> my belief is that the cloud _is_ cheaper than on prem but it is difficult to configure it to be so.
It takes discrete effort in the core planning of your architecture. You cannot look at AWS resources (or any other cloud provider) as an all-you-can-eat buffet. You have to look at your requirements, look at the viable options that may support your requirements and take into consideration cost associated.
Without looking at cost during design your company/service/team will have a bad time at some point. There are also some really specific things you can do to lower costs but require knowledge and understanding of a myriad of technologies.
- pwarner 4y agoyou can and should look at them as aN "as little as you can eat buffet" option. the cost transparency is a huge part of the value of cloud, even if it cost the same as on prem, the transparency is huge, but it's even more valuable if you make smart choices with that transparency. of course often folks just ignore costs until al of the sudden it's a huge pain point.
- notyourwork 4y agoOur team typically expects some cost consideration given in design documents. This way we know that some attention was given to it and it's a good starting place for discussing costs during design review.