Content Systems Architecture: Approaches in a decoupled world
- 1. Content Systems Architecture Approaches in a decoupled world Dominic Laycock @dtlaycock July 17th 2019
- 2. Content Platform • Multi-source • Multi-channel • Microservices
- 3. @dtlaycock “A loosely coupled system that is easy to maintain and change as it evolves.”
- 4. Leyla Acaroglu - https://www.disruptdesign.co/
- 5. Image credit Steve Czajka via Flickr, Creative Commons
- 10. Content Silos
- 11. @dtlaycock The first step to decoupling
- 12. Just a paint job?
- 13. Integration
- 14. @dtlaycock
- 15. @dtlaycock MVP Content Platform • Smaller blocks of code • Platform autonomy • Abstraction
- 16. Retrospecting
- 18. Canonical data • A unifying format • Content and relationships • Integration point
- 19. Canonical data • A unifying format • Content and relationships • Integration point
- 20. Canonical data • A unifying format • Content and relationships • Integration point
- 23. @dtlaycock Offloading complexity What we own and maintain
- 24. @dtlaycock Offloading complexity What we control via configuration
- 27. @dtlaycock –Diana Montalion “Teams that cultivate emergent behavior build emergent systems.” Socio-technical
- 28. • Summary • Why • What • Who • How • When (ish) By Aleksandr Andrushkiv, Shutterstock.com Socio-technical Top Down Elaborations (TDE)
- 30. @dtlaycock Build content systems for emergence • Canonical data model - Build on top of your content • Asynchronous communication - Choreography over orchestration • Connections - Offload complexity to services where possible • Design for change - Store data in industry standard formats • Socio-technical - Embody the characteristics of the system you’re building
- 31. Uniqueness