# Tailscale Authors - Modules, Monoliths, and Microservices (Highlights) ![rw-book-cover|256](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) ## Metadata **Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png **Source**:: #from/readwise **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Tailscale Authors]] **Full Title**:: Modules, Monoliths, and Microservices **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [tailscale.com](https://tailscale.com/blog/modules-monoliths-and-microservices/) **Host**:: [[tailscale.com]] **Highlighted**:: [[2021-03-06]] **Created**:: [[2022-09-26]] ## Highlights - By far the part we're worst at is #1, isolation. - Cloud VMs default to passwordless sudo, because root vs non-root isolation turned out to be weak, so why even bother. - Shared libraries and DLLs from multiple vendors get linked into apps from other vendors because all the code is assumed trustworthy. - you almost never define module boundaries for security reasons. Instead, module boundaries typically follow Conway's law. People break up modules based on how they want to subdivide the development work on their team, and modules end up communicating based on how the teams and teammates communicate.