This is an excerpt from the Designed Analytics report: Business 4.0: Becoming a Technology-Driven Enterprise.
The first challenge with the traditional view of this architecture or architectures across multiple industries, is that they are designed as technical architectures. You can easily see, specifically if you think about the examples we have shared in the previous chapters, that many of these systems need to interact with each other in more dynamic ways, beyond the vanilla enterprise service bus architecture. The siloed technical view of architecture leads to numerous challenges, the primary one being that these systems end up being used inefficiently.
The good news is that businesses do not need to replace these existing systems. The crux of the platform approach is to integrate these systems, leveraging existing, and emerging technologies, in a way that allows organizations to harness technology beyond operational and informational aspects, into strategic aspects. Let us explore this perspective with an example interaction from the complete architecture shown in Figure 9.

The first challenge with the traditional view of this architecture or architectures across multiple industries, is that they are designed as technical architectures. You can easily see, specifically if you think about the examples we have shared in the previous chapters, that many of these systems need to interact with each other in more dynamic ways, beyond the vanilla enterprise service bus architecture. The siloed technical view of architecture leads to numerous challenges, the primary one being that these systems end up being used inefficiently.
The good news is that businesses do not need to replace these existing systems. The crux of the platform approach is to integrate these systems, leveraging existing, and emerging technologies, in a way that allows organizations to harness technology beyond operational and informational aspects, into strategic aspects. Let us explore this perspective with an example interaction from the complete architecture shown in Figure 9.
A customer wants to open a wealth management account with a bank where they currently have a checking account. They would have few different types of interactions, as covered in Chapter 5. These interactions, eventually are the reason that the entire portfolio of architecture exists-to serve the customer.

The mix of agility and efficiency in technical architecture can become a reality by a hybrid architecture of event bus, and a smart enterprise bus. And that requirement can be best understood when we categorize the types of interactions in the way shown in Figure 10.


