How Composable Architectures can actually solve the reasons for Microservices

Many companies today want a faster time-to-market, more flexibility, and scalability for their digital services. Investments are often made in IT for this, such as a “migration to the cloud” and developing “microservices”. However, the result is often that such a transition and development becomes more complex and more expensive, instead of being able to take advantage of the anticipated benefits. So what causes this? Which aspect is missing from the application of cloud infrastructure and microservices? What can you do to make them beneficial? This is where Composable Architecture comes in! In this session, I will 1) Elaborate on Composable Architecture and how we got there; 2) Define the value of applying composable architectures using the Composable Enterprise as a framework; 3) Share how I applied Composable Architectures in projects, and what I learned from it

Transcript

1. HOW COMPOSABLE ARCHITECTURES CAN ACTUALLY SOLVE THE REASONS FOR MICROSERVICES
3. • Principal Consultant with Team Rockstars IT • Java Champion • Loves solving complex, strategic IT challenges • Passionate about collecting and sharing knowledge about improving IT in organizations • Adept with cloud-driven software development in general • Frequent Conference Speaker EDWIN DERKS
4. Let’s start with… A simplified view of traditional IT
5. Email CRM HR Office Identity Printing Customized Software 1 Customized Software 2 Firewall DMZ Integration Disaster Recovery Infrastructure Back-up Off-site Hosting IT Services Office Automation An Enterprise Architect’s view of a business
6. IT infrastructure in practice Email CRM HR Office Identity Printing Customized Software 1 Customized Software 2 Firewall DMZ Integration Disaster Recovery Infrastructure Back-up Off-site Hosting IT Services Office Automation Do you recognize: • Tight Coupling • Scalability conflicts • Data inconsistency • DR and back-up strategy gaps ?
7. Email CRM HR Office Identity Printing Customized Software 1 Customized Software 2 Firewall DMZ Integration Disaster Recovery Infrastructure Back-up Off-site Hosting IT Services Office Automation Who owns… what? CxO IT Manager Product Owner ? Do you recognize: • Misaligned ownership • Out-of-sync backlogs • Incompatible interfaces or protocols • Feature gaps
8. The Solution…? Let’s move to the cloud and build Microservices with Domain Driven Design
9. Monolithic Application Database Microservice Data- base Microservice Data- base Microservice Data- base Development challenges that come for free with Microservices: • Cloud migration and adoption • Distributed transactions • Eventual consistency • Unclear source of truth • Distributed monolith • Duplicated data • Misaligned responsibilities • Back-up complexity • Complex release trains • Exponentially increasing maintenance • Increased cost of development and infrastructure • Version inconsistency and Incompatibility • Observability and security gaps The perils of a moving to the Cloud and building Microservices
10. The Solution that should be… Let’s move to the cloud and build Microservices with Domain Driven Design
11. The Problem…! DevOps, Microservices, Domain Driven Design are not enough to make modern IT actually work
13. Composable Enterprise Domain Driven Design… for the business
15. Packaged Business Capability (PBC) • Represents a single, self-sustaining unit of business with mandate and governance to manage itself • Designated skills for people building, maintaining and operating the business logic • No direct dependencies on other business units through API integration and event driven communication
16. Composable Architecture: Microservices with a touch of BizOps Not Composable Micro Service Data- base Micro Service Data- base Micro Service Data- base Processes Composable Micro Service Data- base Micro Service Data- base Micro Service Data- base Processes
17. 1. Enterprise Vision on digital transformation 3. Enterprise Integration Platform 2. Business Development Teams Packaged Business Capability (PBC) Three ingredients for building a PBC
18. 1. Enterprise Vision on digital transformation IST SOLL • The enterprise IT roadmap for the modularization and digital transformation of the organization • Includes strategic aspects of the desired business and IT alignment • Provides architectural guidelines, principles and decisions for developers • Break up processes so that every business aspect ultimately falls into a certain PBC
19. 2. Business Development Teams • Dedicated teams for delivering business value, matching their purpose and capabilities • Supporting teams for sustaining business on IT infrastructure • There is a limit on how T-shaped people can become Complicated Subsystem Teams Enabling Teams Platform Teams Stream Aligned Teams
20. 3. Enterprise Integration Platform • Scalable hosting and development infrastructure, provided as a (self) service for developers • Built and maintained by Platform Team(s) with expertise in cloud infrastructure • Provides generic cross-cutting concerns that take complexity out of software solutions for business services • Governed by a competence center for sustainability of knowledge, consisting of different kinds of expertise ranging from technical to legal Competence Centre Logging Integration Monitoring Database IAM File Storage CI/CD Configuration Messaging Authorization Packaged Business Capability (PBC) Cloud Infrastructure PlatformOPS
21. Infrastructure IT Services 3 IT Services 2 IT Services 1 Architecture Platform Sales Application Office Automation Security HR Business Intelligence Enterprise Integration Platform Cloud Provider + DR On Premises SaaS Service 1 SaaS Service 2 Enterprise Vision Business Development Teams Stream-Aligned Team Enabling Team Platform Team Complex Subsystem Team
23. Composable Architecture: Key Takeaways The IT infrastructure must follow the enterprise vision to align properly with the business Business value, processes and domain knowledge must be componentized within separate PBCs that must be able to function completely autonomously in terms of business operations and IT Business operations within a PBC must be conducted by people with the necessary domain knowledge and technical skills 1 2 3
24. Composable Architecture: Where to start? Spot a system or team within the company that is not operating smoothly due to mandate, integration or function in the IT infrastructure Set up the functional boundaries using (Team) APIs and other methods for achieving this. This way, you define the boundaries for the business domain of the PBC Optimize the technical and functional skills of the colleagues who will perform the PBC. A skill gap matrix can be an excellent tool for this Adopt as many cross-cutting concerns of underlying IT infrastructure as possible, so that you increasingly work towards an Enterprise Integration Platform 1 2 3 4
25. RATE MY LECTURE! Go to eventory app • Find my lecture in the agenda • Click on it and rate the lecture
26. THANKS FOR YOUR ATTENTION EDWIN DERKS Team Rockstars IT @edwinderks