Today I received an email from a Cloud service provider, reporting the lessons learned from a general problem they had with their connectivity services to the public network and their dependencies.

The point is that although in terms of datacenter, many times the answer to these problems for rapid recovery from adversity is redundancy, in terms of data architecture and in general in architecture, the solution is not always to duplicate to be resilient to failures.

A few years ago, talking with a colleague, I explained how to segment the data catalog into domains, thus obtaining a logical and physical separation between the needs of the different domains. This would give us the benefit of being able to create solutions with a decoupling of the requirements of two different domains and also with this that the modifiability of an application / data entity of domain "A" does not imply an indirect cost in an application or data domain. domain "B".
This is how we addressed in this talk the concept of semantic coherence, a concept already well known (but little applied in general) that in my opinion is key to solving a quality attribute in the design of an architecture such as resilience management. I recommend this read on Mesh Data which is very interesting..

This is a very named concept, directly or indirectly today when talking about microservices, apis, kubernetes, etc. All of them, concepts that aim to decouple responsibilities in the architectures and create a high resilience against failures and the need for horizontal scaling among other concepts such as cohesion management.

A more extended summary of this matter in terms of data, is what I write in the article Data Lake is more than 'dump your data here' . Article I wrote motivated after that talk I mentioned about domain segmentation.

Also, I refer to this, when I talk about a definition of the meaning of IT architecture, when I comment that architecture is not only about designing applications and defining the rules of the game, but how these applications are related in a strategy ---> IT architecture and the importance of the relationships

Dependence is the enemy of resilience, a phrase that I liked a lot to define why semantic coherence is a practice that should be on the design board when designing and generating an architecture.

I think that thinking in terms of the decrease in dependencies between domains, dependencies between applications, dependencies with providers opens a new paradigm that is already heard in the market in general but not yet very frequently, about multiCloud / HibridCloud.

Tks.