4 ms·
Nitpicking: from an architectural point of view, I don't see why you would opt for "build you own cloud on top of Amazon", as opposed to leveraging the Amazon s
by ToJans 9y ago
Nitpicking: from an architectural point of view, I don't see why you would opt for "build you own cloud on top of Amazon", as opposed to leveraging the Amazon stack, especially because the author points out it is a small team.
Maybe it's a resource issue, or they need some things that cost too much money on Amazon, but the author should at least justify why kubernetes was chosen.
My apologies for ranting about this, but I've seen this approach way to much, wasting valuable company dollars.
- emforce 9y agoI don't believe it would be a case of building your own cloud on top of Amazon, it would be a case of saying something like: I want 2 instances of my account service, 2 instances of my comic-book viewer service behind a load balancers. You are specifying how you want your application to look as opposed to a fully fledged cloud offering. I hope this clarifies things!
- ToJans 9y agoOk, looks like I misunderstood. Thank you for clarifying...