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:

  1. Client UI - typical client UI to serve channels like web, mobile, email, Social, AR/VR, Kiosk
  2. Infrastructure - this includes networking, security, hosting, routing and other typical functions
  3. 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
  4. Data storage - storage and persistence for data and analytics. Enterprise Data Lakes, Collections DB etc.
Non-composable version of a digital solution will still include these layers but they are siloed.

Layers in non-composable solution

Decomposing the digital solution into these basic layers is in other terms is achieved through decoupling of technology. 

Composable layers

The idea is rather simple. Customers and employees interact across channels with client UI. The user's interactions on the UI generate requests that are handles by appropriate Infrastructure which hosts business applications. The users interactions, request routing, application logging etc. all generate data which is persisted at scale within the data layer.

This now starts to resemble Composable DXPs like Sitecore, Optimizely, Adobe, Acquia.

In case of home grown, bespoke digital platforms, decoupling all four can be achieved but will end up being too complex and too expensive to maintain.

So where do SaaS products feature into the composable story?

Let's take this decomposition at bit further. The layers further breakdown into composable blocks of their own.
  1. Client UI  - let's say breaks down into basic building blocks like HTML/CSS, JavaScript,  JSON, GraphQL, OData 
  2. Infrastructure - breaks down into Hybrid Cloud,  API Gateway, SaaS API endpoints
  3. Platforms/products - break down into self hosted or self managed products vs SaaS stacks
  4. Data storage - includes platform data, customer data, engagement analytics, content indexes
Composable stacks and suites

As you can see SaaS plays a role in almost all the layers. This picture also starts to draw a line between monolithic suites vs SaaS based composable stacks. 

In the next article, we will add a orchestration layer to show how the composable architecture can truly take shape.

Comments

Post a Comment

Popular posts from this blog

First look at Sitecore XM Cloud: Part 4 - Creating a new Site

Image
 Once you have successfully create an environment, you can go ahead and create your first site. In order to create a new Site, you need to launch the Sitecore Launchpad by clicking on the "XM Cloud Launchpad": Click on "Sites" menu to create a new Site: Click on "Add your first website" button to start the wizard. I chose the "Basic Site" template: Enter a Site name and pick a language and click on "Create website" button. You will see the following screen while your Site is being created: Once the Site is created, you can edit it in Pages or Explorer using the context menu: Explorer view of the Site: 1. "Details" view of page. 2. "Content" view of page: Unfortunately, trying to load the new Site in pages gives "Unable to connect to remote server"
Read more

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields: org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766> Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766> This is due to the fa...
Read more

First look at Sitecore XM Cloud: Part 1 - Getting started with Sitecore Cloud Portal and XM Cloud Deploy

Image
The biggest news of the year in the Sitecore community has been the arrival of Sitecore XM Cloud. In this blog series, I will be showing partner's access to XM Cloud. To get started, one needs to be invited to Sitecore Portal. You can access it at https://portal.sitecorecloud.io/.  Once you create an account and sign-in, you arrive at the following screen which has two main actions: Invite members  Managed projects (Sitecore XM Deploy) If you look closely you will see Sitecore Cloud Portal and XM Cloud Deploy. Invite team members opens up the following screen: "Manage My Projects" option launches the following window In the Part 2 , I will take us through deploying our first XM Cloud instance.
Read more