Chopping the monolith

on YouTube ↗33m

" summary

Argues that only hot-changing capabilities need independent deploys and proposes a middle path: keep stable core and move fast-changing parts to FaaS. Shows a concrete migration of a pricing module from a Java monolith into Azure Functions, fronted by Apache APISIX configured via etcd, with Docker Compose and a SQL backend. Notes provenance in rule engines, claims serverless reduces lead time, and reports the live demo routing to Azure failed once but worked in prior runs.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 1:11Microservices hype reality
3. 4:27Conway’s law and teams
4. 9:47Why microservices fail
5. 15:02Legacy deployment struggles
6. 21:08Strangling the monolith
7. 22:36Live demo setup
8. 32:01Q&A and resources

" related talks

• 35mChopping the monolithNicolas Fränkel · DevConf.CZ 2023
• 31mChopping the monolithNicolas Fränkel · Heapcon 2022
• 37mChopping the monolithNicolas Fränkel · Voxxed Days Cluj-Napoca 2022
• 42mChopping the MonolithNicolas Fränkel · Øredev 2023
• 42mChopping the monolithNicolas Fränkel · Devfest Strasbourg 2023
• 45mThe Evolution From Monolith to Microservices to Serverless and BeyondHugh McKee · Voxxed Days Microservices 2019
• 42mHelp! I've created a serverless monolith!Marc Duiker · NDC Oslo 2022
• 33mFireside chat - Monoliths, Microservices & Modernization – Practical StrategiesIvan Brezak Brkan, Bruno Kovacevic · Infobip Shift 2021