In this session, we'll look at the multitude of challenges of achieving polyglot persistence nirvana, and strategies for addressing associated risks.
It always sounds easy - "use the best tool for the job". With very isolated systems, it's easy to decide RDBMS for one application, Redis for another and Cassandra for somethings else. When it comes time to building systems with multiple persistent stores, we're met with challenges in integration, existing applications, and push back from IT administrators. In this session, we'll look at the multitude of challenges of achieving polyglot persistence nirvana, and strategies for addressing associated risks.
YOU MAY ALSO LIKE:
- The JVM as a platform for building smart contracts (in London on 28th June 2017)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 1st - 3rd November 2017)
- µCon 2017: The Microservices Conference (in London on 6th - 7th November 2017)
- Fast Track to RESTful Microservices (in London on 8th - 10th November 2017)
Real World Polyglot Persistence
Jimmy is a member of the ASPInsiders group, the C# Insiders group, as well as being the "Microsoft Most Valuable Professional" (MVP) for ASP.NET since 2009. He is also the creator and lead developer of the popular OSS library AutoMapper.