In our previous article from this series we introduced a use case around headless e-commerce for retail stores. The process was laid out how we’ve approached…
Join the DZone community and get the full member experience. In our previous article from this series we introduced a use case around headless e-commerce 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 architectural blueprint. The only thing left to cover was the order in which you’ll be led through the blueprint details. This article starts the real journey at the very top, with a generic architecture from which we’ll discuss the common architectural elements one by one. This will start our journey into the logical elements that make up the headless e-commerce architecture blueprint. 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 blueprint that was uncovered researching those solutions. It’s our intent to provide a blueprint that provides 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 architectural blueprint, 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 blueprint and outline the solution. 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 architectural blueprint. It’s our intent to provide a blueprint 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 architectural blueprint 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 architectural blueprint. 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 my research. As you notice from the beginning, this logical diagram starts with a focus on cloud native development and the developer.
