Tolerant Reader Pattern

Reading and writing configs and objects can be more challenging than it looks. As your application evolves and your contract is used across several services, you might need to have Backward Compatibility. Easily we can think about 2 scenarios, the first scenario let's say you have a distributed monolith and you have multiple apps using the same database. The second scenario considers you have an Event Sourcing + CQRS application using Kafka for instance where you emit and read domain events. In both scenarios, there will be breaking changes, so how we can make your parsers and serializers to be more efficient and resilient to change, well: The Tolerant Reader Pattern is here to rescue.

The Video

The Code

https://github.com/diegopacheco/java-pocs/tree/master/pocs/design-patterns

Cheers,

Diego Pacheco

Popular posts from this blog

Podman in Linux

Java Agents

Manage Work not People