Designing an Extensible Billing Platform using Domain-driven Design

on YouTube ↗30m

" summary

Atlassian replaces a 20+-year monolith by building a new billing platform from scratch (Commerce Cloud / CCP), using Domain-Driven Design to split billing into bounded contexts (orders, subscriptions, payments, promotions, quotes) each backed by microservices, an event-driven stack (Streamup) and headless API-first integration. The system models multiple pricing strategies (seat, usage, overage), encodes rules as pure config (including a synthetic pricing plan for special pricing) and cuts product onboarding from months to about two weeks via ubiquitous language and loose coupling.

AI-written summary · about

" chapters (7)

1. 0:00Vision and requirements
2. 3:32Legacy system challenges
3. 6:42Engineering guiding principles
4. 10:22Domain driven design overview
5. 15:32Ubiquitous language importance
6. 21:42Platform design and architecture
7. 28:18Summary and conclusion

" related talks

• 42mHigh-Speed DDD (revisited)Thomas Pierrain · Devoxx France 2024
• 47mDomain-Driven Design: A Complete ExampleEberhard Wolff · JCON EUROPE 2024
• 45mE-commerce platform. Core build principles, problems and guidelines.Bogdan Shorokhov · Devoxx Ukraine 2021
• 48mPlatform Engineering is Domain Driven DesignGregor Hohpe · DDD Europe 2025
• 40mMonolith Explosion into Multidisciplinary TeamsXavier Belloso, Marcos Mañas · CAS 2019
• 01h 02mDeconstructing Monoliths with Domain Driven Design - Rohit Kelapure, David Turanski, Rohit SoodRohit Kelapure, David Turanski, Rohit Sood · SpringOne Platform 2017
• 58mModernizing an existing system to take a more domain-driven approachWilliam Penberthy · NDC Sydney 2020
• 48mDomain Driven Design: The Good PartsJimmy Bogard · DevConf 2019