Your software architecture may aid global warming
summary
Claims that default microservices often cost more energy and complexity, citing a measured case where splitting into microservices raises CPU/energy from 3x monolith to 10 (authors note missing network/DB overhead), internet emissions match the global airline industry, data centers use ~33% of ICT energy and Amazon reports ~90% cost drop after reconsolidation. Proposes a modular monolith pattern and shows tooling: dependency rules with ArchUnit and background work with JobRunr. Language energy examples: Java ~2x C, JavaScript ~4x, TypeScript ~21x.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:53Microservice architecture
- 4:00Energy consumption
- 6:30Improving software
- 9:33Modeler model
- 10:18Tools
related talks
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
49mNowadays Architecture Trends, from Monolith to Microservices and Serverless
55mIs it Time to Abandon Microservices? Modular Monoliths Rescue Your Wallet!
23mLightning Talk: Rethinking Microservices
39mConsidering Migrating a Monolith to Microservices?
43mMonolith? Microservices? Who cares?
26mEnhance System Resilience and Efficiency with Microservices
20mMicroservices in the future