4 ms·
You can also predict the costs, and shop around if your provider gets greedy. If Amazon changes its pricing structure, what are you supposed to do?
by nicbou 6y ago
You can also predict the costs, and shop around if your provider gets greedy. If Amazon changes its pricing structure, what are you supposed to do?
- ajsnigrutin 6y agoIt's a lot easier to change providers, if your service is an (eg.) docker image(s), than to move something relying on amazons api.
- xorcist 6y agoIt's even easier if your application is just (an equivalent of) a binary, or a tarball.
- ForHackernews 6y agoUnless it relies on any system libraries, in which case you're in dependency hell when you upgrade or change the OS.
- joana035 6y agoThis is a solved problem, and dependency hell happen when not choosing dependencies wisely when creating programs.
- VHRanger 6y agoIf you built everything in proprietary infrastructure, porting is a lot more work. Using lambdas tie you to AWS because as soon as you use a few step functions, or you have a few lambdas interacting, changing to Azure or GCP becomes a huge pile of dev work and QA. Having everything "just run" on linux instances let you be perfectly portable and now you can actually shop around.