Business Optimisation Architecture - Example Planning Optimisation - In my previous article from this series I shared the logical view of the business optimisation use case for retail stores.
In my previous article from this series I shared the logical view of the business optimisation use case for retail stores.
The process was laid out how I've approached the use case and how portfolio solutions are the base for researching a generic architectural blueprint.
It started with laying out the process of how I've approached the use case by researching successful customer portfolio solutions as the basis for a generic architectural blueprint.
Having completed our discussions on the logical view of the blueprint, it's now time to look at a specific example.
This article walks you through an example optimisation scenario showing how expanding the previously discussed elements provides a blueprint for your own optimisation scenarios.
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 my 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 I've chosen a format that I hope makes it easy to absorb. Feel free to post comments at the bottom of this post, or contact me directly with your feedback.
Companies need to be thinking long-term before even starting a software development project. These needs are solved at the level of architecture: business owners want to assure agility, scalability, and performance.
In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.
Microservices are growing as the default architectural design pattern. But why has it become such a point of emphasis? Find out here.
In this article, look at different ways to test microservices and how you can have a suitable testing strategy to begin with.
In this article, you will learn what are Microservices? Many people have many perspectives on Microservices, and there are many definitions. I recommend, rather than going by the definition, go by characteristics.