Part 2 - Decomposing and decoupling to achieve composability
Having introduced "composable" in part 1, we will now look at deconstructing and decoupling the typical layers of a digital solution to understand how composability can be achieved within them.
Let's assume a typical application is composed of the following four layers:
- Client UI - typical client UI to serve channels like web, mobile, email, Social, AR/VR, Kiosk
- Infrastructure - this includes networking, security, hosting, routing and other typical functions
- Platforms/products - Off-the-self, plug-and-play, pay-as-you-go, bespoke products and tools that offer packaged business capabilities (PCBs is another Gartner term) or business applications as well as persistence
- Data storage - storage and persistence for data and analytics. Enterprise Data Lakes, Collections DB etc.
- Infrastructure - breaks down into Hybrid Cloud, API Gateway, SaaS API endpoints
- Platforms/products - break down into self hosted or self managed products vs SaaS stacks
- Data storage - includes platform data, customer data, engagement analytics, content indexes