3 ms·
I like how being full-stack is 'legacy'. I do understand the separation of concerns though: once you are big enough to afford a team of sysadmins and infrastrct
by Spivak 9y ago
I like how being full-stack is 'legacy'. I do understand the separation of concerns though: once you are big enough to afford a team of sysadmins and infrastrcture people you can provide your devs in-house PaaS and IaaS.
- dullgiulio 9y agoAll is well if you are cooking pizza. But if you are cooking meth, the kitchen the XaaS provide will not do any more. Full stacks are legacy unless you need them customized. For example, not everyone is doing the horizontal scalability trick. In the large enterprise, Oracle on one big iron is common, so common the newest versions actually concentrated improvements for those use cases, unlike what the marketing department keeps advertising.
- unit91 9y agoYeah, legacy is probably a bad term because it connotes "old". Still, there is a sense in which this is the legacy approach: very few do it, whereas it used to be the norm. In fact, the only place I've ever worked that self-hosted and loved it was the Air Force. Three other companies I've worked for haven't self-hosted at all, and one very large, established company had an active offload-to-AWS plan.