4 ms·
> Given a non leaky abstraction, ignorance of whats under the hood is just fine. Minus vendor lock-in. Once you have your infrastructure dependent on ELB, S3,
by sergiosgc 11y ago
> Given a non leaky abstraction, ignorance of whats under the hood is just fine.
Minus vendor lock-in. Once you have your infrastructure dependent on ELB, S3, Redshift and all the other AWS niceties, you are effectively locked into Amazon. Locked, in the sense that migrating out has a relevant knowledge cost (deprecation of knowledge of AWS, need for gain in alternative knowledge).
It's not a dumb choice, but it's also not clear for either side. Running your own iron is much much cheaper. For my case (email service provider), our bill estimate on AWS would be about 300k€/year, while running our own servers costs 84k€/year (split at 48k€ depreciation and 36k€ operational costs).
- toomuchtodo 11y ago> It's not a dumb choice, but it's also not clear for either side. Running your own iron is much much cheaper. For my case (email service provider), our bill estimate on AWS would be about 300k€/year, while running our own servers costs 84k€/year (split at 48k€ depreciation and 36k€ operational costs). Something to note about US orgs: New depreciation rules allow you to depreciate $500K/year in hardware, in that year. That means that gear is yours, forever, whereas that $500K/year in opex to AWS is recurring forever.
- pnathan 11y agocan you link to a detailed analysis of that?
- toomuchtodo 11y agoDid you want a link to the new depreciation rules? Or a specific scenario?
- pnathan 11y agoLink to the rules, and/or some analysis by a well-regarded accountant. I'd like to route the information internally. :-)
- toomuchtodo 11y agohttps://www.irs.gov/publications/p946/ch02.html https://www.irs.gov/publications/p946/ch02.html is the relevant IRS publication.