Architecture · 2019–now · Platform Wars
Data mesh
Decentralize data ownership like microservices for warehouses. Real org problem; often a logo refresh for the same broken pipelines.
Data mesh mutated into useful platform and ownership ideas — and failed as a silver bullet when companies bought the vocabulary without fixing incentives. The fad was renaming the data lake. What sticks is domain ownership with actual platform support; what fades is mesh without metrics.
Cost of the fad
Consultancies sold domain ownership and federated governance while teams still could not agree on a customer ID. Slideware outpaced catalog tooling by years.
Patterns
Context
Frameworks fought for the runtime
Front-end frameworks consolidated power; TypeScript became the floor; serverless and Jamstack rebranded old ideas with better CDNs. Blockchain-for-CRUD and big-bang rewrites collected the decade’s dumbest budgets. The winners were boring platforms with ecosystems. The losers were narratives that skipped product-market fit.
Compare with
Related
Architecture · 2012–now
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most.
$ Teams split 4-person products into 40 services, then hired SREs to babysit the mesh. Many later consolidated — after years of distributed tracing invoices and on-call trauma. See case studies on premature microservices and big-bang cutovers for named failure modes.
Platform · 2011–now
Apache Kafka
Durable log as nervous system. Event-driven architecture with real operational teeth.
Platform · 2006–2018
Hadoop Everywhere
MapReduce as lifestyle. The elephant in rooms that needed a spreadsheet.
$ Enterprises stood up Hadoop clusters for gigabytes of data that fit on one Postgres instance. Hadoop admins, ZooKeeper nightmares, and ETL rewrites burned millions before Spark and cloud warehouses retired the elephant.
Platform · 1974–now
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.