4 ms·
Just want to highlight how futuristic the author's title is: "Computational Biologist, Head of Protein Design @ Enzymit". Why they moved to on-prem: lower and
by lioeters 5y ago
Just want to highlight how futuristic the author's title is: "Computational Biologist, Head of Protein Design @ Enzymit".
Why they moved to on-prem: lower and more predictable cost. At a public cloud provider, they lost thousands of dollars (of free credit they had) through "architectural blunders". And the running cost of GPU, CPU, storage, and data transfer summed up to $10K a month - at which point they figured they might as well purchase their own compute servers.
- tonyedgecombe 5y ago>"architectural blunders" I wonder how much of this is by design. It seems it is in Amazon's interest to keep their systems and pricing as opaque as possible.
- mathattack 5y agoAt MSFT the Azure solutions architects are part of the sales organization. Their commissions are tied to usage (revenue) which tells you everything about their skill sets. And their lack of standard clear pricing means you have to estimate everything yourself.
- maccard 5y agoI've spent a lot of time with Amazon's Architects who have given us a huge amount of advice on how we could reduce our costs. Maybe we've gotten lucky with our contact, but their approach for keeping us on AWS seems to be "provide enough value on top of AWS that the extra pricing doesn't really matter" mostly in the form of handing us architecture templates for common workflows that we've never set up.
- sokoloff 5y agoNow, when they make blunders, they don’t see an overt bill for them and are thereby happier.
- motoboi 5y agoNice to see how this move can be an architectural blunder by itself.