Be the first to like this
Today, it seems everyone is breaking down their monoliths and building microservices applications. However, one challenge that architects struggle with is how to access and protect the data. How do you preserve microservices-style independence when different services need access to the same data? What happens with data consistency? Should you choose a traditional database, a noSQL database, scrap the database and go with a caching solution, or is there another option?
Join Red Hat and NuoDB as we discuss:
The challenges around microservices, data, and breaking down the monolith
Common pitfalls organizations encounter
Examples of use cases and various approaches to handling data in microservices applications.