CMS Monoliths vs Microservices & Composable - Are monoliths so bad? - Arbory Digital Podcast Ep10
Full post: https://blog.arborydigital.com/monoli...
In a world where everything seemingly HAS to be composable or a microservice to be "cool," who's going to speak up for the unloved monolith? Veteran multiplatform DXP architect Brett Birchbach from DX-ROI (https://www.dxroi.com/) and Arbory Digital Principal Architect Tad Reeves discuss the differences between monolithic, composable and microservice-based CMS solutions and reasons why each JUST MIGHT be the right tool for the job.
Video Chapters
0:00 - Introductions
1:46 - The pendulum swings of technology
3:46 - Define: what is a Monolith?
5:42 - Is the term "monolith" negative?
7:48 - Define: what is a "composable" site?
9:15 - Defining "composable" vs "microservice"
11:40 - Microservice examples
12:40 - Defining "headful" vs "headless"
17:28 - What about "omnichannel" and old monoliths?
19:52 - The ORM analogy
22:25 - "Tech stack lock-in" myths & truths
25:30 - Microservices can save the day - like AEM Asset processing
29:15 - "All monoliths have performance problems" myth
32:32 - A known vs unknown set of performance characteristics
37:36 - Can you find experts for all of your system's constituent parts?
40:10 - Long-term budget considerations
44:23 - Some organizations "just aren't ready for composable"
51:02 - Now you have to get REALLY good at documentation
52:53 - Key questions for a future-architecture evaluation
56:25 - Analogy - the forced cloud migration
58:12 - The conference hype train