<story><title>Running a modern infrastructure stack</title><url>https://blog.barricade.io/running-a-modern-infrastructure-stack/</url></story><parent_chain></parent_chain><comment><author>skywhopper</author><text>Hmm, this is the second such post I&amp;#x27;ve seen recently that lays out the company&amp;#x27;s infrastructure stack and after a few points, it mentions how they&amp;#x27;ve outsourced all their logging and alerting to DataDog who solved all their problems in that area. DataDog seems like a nice product, and I know nothing about it, but after seeing how ... aggressively they were marketing at re:Invent, color me skeptical that these stack discussions are entirely spontaneous.</text></comment>
<story><title>Running a modern infrastructure stack</title><url>https://blog.barricade.io/running-a-modern-infrastructure-stack/</url></story><parent_chain></parent_chain><comment><author>mwcampbell</author><text>Have you looked at Joyent&amp;#x27;s Triton service? They claim they can run containers securely on bare metal, since the underlying kernel is Illumos (but it can run Linux binaries and thus Docker containers). So the trade-off between isolation and efficient resource usage would disappear.&lt;p&gt;On the one hand, they don&amp;#x27;t have all the same higher-level services as AWS, like ELB, let alone managed database services. On the other hand, I don&amp;#x27;t think I&amp;#x27;d sleep well running anything based on EBS ever again, since EBS is so notorious for cascading failures.</text></comment>