Member-only story
Cloud-Native Architecture Patterns (Part 2)
Anti-Corruption Layer, CQRS, Event Sourcing
Since Cloud-Native applications get extremely popular and almost all companies build their new systems on cloud nowadays, different patterns addressing cloud specific problems get popular as well. As I mentioned in first part: Software Architecting might take a slightly different approach in applications that are build in cloud-native environments. These applications should be able to run in dynamically orchestrated and containerized environments in order to take advantage of cloud computing model.
Cloud native computing is an approach in software development that utilizes cloud computing to “build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds”.
Please see Part 1 for more Patterns:
Cloud-Native Architecture Patterns (Part 1)
Let us take look at more Patterns, that are, for more point of view, very handy tactics If you collide with relevant problems.
Anti-Corruption Layer…
This Pattern might be very helpful if you have different subsystems or microservices that don’t share same semantics. Anti-corruption Layer translates or integrates communication between those services. This pattern was first described by Eric Evans in Domain-Driven Design.
This kind of constellation can very well happen if you are in progress of migrating legacy system to new ones and party news systems use resources of functionalities of legacy systems.
Drawbacks and Side effects might be following:
- this extra layer adds more latency
- this layer is also additional service that will take up resources
- Maintainability, Data Consistency, Auto-Scaling together with connection services cost also extra attention
Command and Query Responsibility Segregation…
This pattern bases on SoC (Separation of Concerns) in terms of database reads and updates. In traditional architectures, the problem of…
