Supply chain integration - Common architectural elements
The only thing left to cover was the order in which you'll be led through the architectural details. This article starts the real journey...
Join the DZone community and get the full member experience.Join For Free
In our previous article from this series we introduced a use case around supply chain integration for retail stores.The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. The only thing left to cover was the order in which you'll be led through the details.
This will start our journey into the logical elements that make up the supply chain integration architecture.
As mentioned before, the architectural details covered here are base on real solutions using open source technologies. The example scenario presented here is a generic common architecture that was uncovered researching those solutions. It's our intent to provide guidance and not deep technical details.
This section covers the visual representations as presented, but it's expected that they'll be evolving based on future research. There are many ways to represent each element in this architecture, but we've chosen a format that we hope makes it easy to absorb. Feel free to post comments at the bottom of this post, or contact us directly with your feedback.
Now let's take a look at the details in this architecture and outline the solution.
From specific to generic
Before diving in to the common elements, it might be nice to understand that this is not a catch all for every possible supply chain integration solution. It's a collection of identified elements that we've uncovered in multiple customer implementations. These elements presented here are then the generic common architectural elements that we've identified and collected in to the generic architecture.
It's our intent to provide an example for guidance and not deep technical details. You're smart enough to figure out wiring integration points in your own architectures. You're capable of slotting in the technologies and components you've committed to in the past where applicable. It's our job here to describe the generic components and outline a few specific cases with visual diagrams so that you're able to make the right decisions from the start of your own projects.
Another challenge has been how to visually represent the architecture. There are many ways to represent each element, but we've chosen some icons, text and colours that we hope are going to make it all easy to absorb.
Now let's take a quick tour of the generic architecture and outline the common elements uncovered in our research.
Without a doubt, every modern organisation engaged in business optimisation has seen the value of containers and use of a container platform. The container platform provides for one consistent environment for developers and operations to manage services, applications, integration points, process integration, planning services, and security.
It's also the one way to ensure you can uniformly leverage the same container infrastructure across a hybrid multicloud environment. It avoids becoming locked into any private or cloud infrastructure as you have an exit strategy with a container platform that's consistent across your architecture.
There are a few elements worth mentioning, first off the use of supply chain microservices for centralising all interactions with supply chain relevant systems of record and provides access to other services. An api management element for well defined access to services and events, and both message transformation and event streaming services to react and transform communication messages across the platform. Finally, there are elements representing collections of integration microservices and integration data microservices for storage service access.
The security aspect is interwoven in the container platform, as each container service, application, or integration can be plugged in to an organisations authentication and authorization mechanisms.
These elements in the common architecture are found in the solutions researched. They were mentioned by name and consisted of an s ingle-sign-on (SSO) that ensures a smooth interaction between processes, authorisation, authentication, and integration services.
The AI / Machine Learning platform, shown with a private cloud icon, can be any modern data platform that are managed and deployed in this organisation's infrastructure to support the retail usage of AI / ML by ensuring access to supply chain data.
There's one more element that represents the external supply chain systems that are integrated with the core elements of this architecture.
As there are often many third-party systems, this element covers basically everything that customers use from partnering vendors. This can be SaaS solutions or any other third-party backend systems.
The storage services uncovered in the research were pretty simplistic and for that reason there's a single physical block storage element. In later articles, when more detail is shown, we'll make a point to mention the link to a separate architecture supporting the retail data framework which is linked to this use case.
This was just a short overview of the common generic elements that make up our architecture for the supply chain integration use case.
Catch up on any past articles you missed by following any published links above.
Published at DZone with permission of Eric D. Schabell, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.