 |
Part 1 - Introduction |
In a past life I spent many hours
researching, creating, explaining, and
publishing portfolio architectures across a collection of application development, domain verticals, infrastructure solutions, and hybrid cloud domains. Most of these concentrated on the application layers and their usage of the infrastructure.
Then I transitioned into the cloud native observability space and observability became the guiding light in my learning path. This quickly led to the realization that the same solution mapping that the previous portfolio architectures brought to organizations struggling with solving hard problems, also applied to the observability world. It's just a matter of a different angle in how we look at those solutions.
Early in 2023 I introduced the first changes to an existing Financial Payments architecture, publishing a short series where observability was included in the solution diagrams. As my learnings in the observability domain continued, this architectural need for a generic view of how to design a cloud native observability solution for any organization remained on my mind.
For the last few months, a small group has been digging into how to define the next generation observability architecture. This article is the first introduction to our findings.