Because Microsoft tried that and (many) people hated it. Monoliths tend to suck, especially when bureaucracy kills great ideas. And then people implement great

Because Microsoft tried that and (many) people hated it. Monoliths tend to suck, especially when bureaucracy kills great ideas. And then people implement great ideas on their own. Now, since they tend to be unconnected, one can go back to the "mother ship" or innovate a system of inteconnects or API's to get them to work together. "In suckage, there's opportunity." In fact Linux and open source in general grew from dissatisfaction with monoliths, and compare the good they've done compared to the dinosaurs in the computer history museum. Many companies gravitate towards monoliths as growth opportunities, and IT managers like "one throat to choke" (heard that WAY too many times. ) but flowers, people, and apps are different for good reason.