Opening the saved copy…
Strangler Fig Pattern - Azure Architecture Center
Learn how to incrementally migrate a legacy system by gradually replacing specific pieces of functionality with new applications and services.
Learning library
Architecture, design patterns, and how real systems work. A reading library, separate from the news feed.
Explore system design
Published dates refer to the original writeup. Older articles are included for their explanations and examples.
Grouping covers the latest 5,000 matching articles. Older articles remain listed individually.
Learn how to incrementally migrate a legacy system by gradually replacing specific pieces of functionality with new applications and services.
Use the Sharding design pattern to divide a data store into horizontal partitions or shards to improve scalability and performance in distributed systems.
Challenges in data processing pipelines, from periodic to continuous models, and discover innovative solutions like the leader-follower model for big data.
Operational simplicity in aodrqew, balancing stability and agility to enhance reliability, reduce complexity, and focus on impactful innovation.
Learn how to smooth intermittent heavy loads by using a queue that acts as a buffer between a task and the service that it invokes.
What is distributed consensus algorithm? Explore fundamentals, CAP theorem and system design patterns, locking and shared state.
Learn how to use an append-only store to record the full series of events that describe actions taken on data in a domain.
Don't try to build a single, unified model for a large domain. Instead DDD advises us to divide such a domain into many bounded contexts with explicit relationships between them.
Explaining the Dependency Injection pattern, by contrasting it with Service Locator. The choice between them is less important than the principle of separating configuration from use.
Learn how the Competing Consumers pattern supports multiple concurrent consumers processing messages received on the same messaging channel.
The microservice architectural style is useful for handling complex systems, but brings its own complexity so should not be used for simpler environments.
Learn about the Bulkhead pattern, which isolates elements of an application into pools so that if one fails, the others continue to function.
Every system ends up with bad data.
On how addition can lower the value of your software and subtraction increase it
An embedded database's architecture and the evolution of its design decisions.
Understand the data structures and architectural choices in distributed version control.
This blog post was written by Dedeepya Bonthu. This is a repost from her Medium article, approved by the author. In stadiums, sports fans love to express themselves by cheering for their favorite teams, holding up placards and team logos. Emoji’s allow fans at home to rapidly express themselves,
This is a guest article by Stanislav Kozlovski, an Apache Kafka Committer. If you would like to connect with Stanislav, you can do so on Twitter and LinkedIn. Originally developed in LinkedIn during 2011, Apache Kafka is one of the most popular open-source Apache projects out there. So far
A new generation of collaborative software that allows users to retain ownership of their data.
CQRS (Command Query Responsibility Segregation) is the notion that you can use a different model to update information than the model you use to read information
Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.
Learn how to load data on demand into a cache, which can improve performance and maintain consistency between cached data and the underlying data store.
Learn how to handle faults that might take varying amounts of time to fix when applications connect to a remote service or resource.
Defining the microservices architectural style by describing their nine common characteristics
Articles will appear after a source check.
End of results
Opening the saved copy…
End of saved text