Semprini

Why do I run my own blog site? Why don't I just post an article on LinkedIn? or WordPress? Firstly, because I like it. And second, because the internet has become homogenised and I hate it. It's all very samey, and bland because it's all been taken over by corporates who are incentivized by screen time, not enjoyment, interest or creativity. Thirdly, by having a domain name and WAF, I can simply expose stuff that I'm playing with to others - AI/ML, data platforms, and pipelines, GraphQL APIs, anything that I want to do a quick PoC on I can demo to my current client.

A couple of contracts back I was consulting as a solution architect at a national retail organisation I ran an experiment as a proof of the cadence which is possible using Data Autonomy.

Shortly after the project went live, I decided to build it again myself using Data Autonomy as realistically as possible. The result was a far better solution in a third of the time & cost.

BI & analytics loves Data Autonomy and event driven architecture. In the operational side of Semantic Hub / Data Mesh, data is already clean and in business form. Data engineering can subscribe to all significant business object changes and metrics can be automatically calculated live. Dimensional modelling also becomes a much simpler process as canonical data is available near real time.

The data engineering and integration teams can become an active part of data governance and data stewardship. Working closely with the business domain SMEs, everyone is on the same page and reporting is simplified.

Data Autonomy is a collaboration of A Holistic Data Fabric/Mesh, RESTful interfaces, RESTful events and enterprise micro-services. Focused around Resource Oriented Architecture (ROA) rather than Service Oriented Architecture (SOA), its purpose is to provide the ability to change rapidly by keeping the level of dependencies constant across the IT landscape.

Standard event driven integration practice is to take data from a system, transform into a middle model and then transform to each destination. Data Autonomy simply says that while we have the data in the middle form, lets save it.

Each business domain must be free to evolve and mature independently as the view of significant business objects evolves. The data governance group with data stewards and SMEs should be responsible for producing domain aligned data product definitions which are then realized into data products. The features of these data products should cover interfaces and persistence for both operational and analytical data.

If you have a "microservice" which exposes an API calling a back end system, you don't have a microservice - you have an API. Your API has wisely used some of the concepts of microservice architecture. Microservice architecture is not an integration architecture, it's an application architecture and applications are responsible for business logic. This distinction is important because the beauty of microservice architecture is both technical and behavioural.

However, I'll extend an olive branch to the API people, no doubt aghast by my blasphemy, by calling them "integration microservices".

Integration microservices are fine I guess, but too often they are used, just as integration is often used, to sweep the legacy monster under the carpet so we don't have to see it - out of sight, out of mind. We implement integration microservices containerised, auto-scaling, auto-healing etc, IT management has an orgasm, we all add something to our CVs and the legacy monster waits.