Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Microservices Applications: Challenges and Best Practices When Deploying SQL-based, Cloud-Native Apps

81 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Microservices Applications: Challenges and Best Practices When Deploying SQL-based, Cloud-Native Apps

  1. 1. Presented by Red Hat and NuoDB MICROSERVICES APPLICATIONS: Challenges and Best Practices When Deploying SQL-based Cloud-Native Apps MAY 23, 2018
  2. 2. Copyright © 2018 NuoDBCopyright © 2018 NuoDB INTRO TO SPEAKERS
  3. 3. Copyright © 2018 NuoDB + + + AGENDA
  4. 4. THE CHALLENGES WHEN DEPLOYING MICROSERVICES & SQL-BASED APPS
  5. 5. TODAY, CIOs REQUIRE MORE
  6. 6. ● ● ● ● ● ● ● ● ● YESTERDAY’S TECHNOLOGIES NO LONGER DELIVER
  7. 7. DATA AND APP MIGRATION ▪ ▪ ▪ …
  8. 8. DATABASE ARCHITECTURE A “MONOLITH” + ▪ • • ▪ ▪ vs.
  9. 9. Copyright © 2018 NuoDB TRADITIONAL DATABASES WERE NOT BUILT TO RUN IN CONTAINERS
  10. 10. To Access and Protect SQL Databases in Microservices Applications DATA STRATEGIES FOR HA MICROSERVICES WITH OPENSHIFT
  11. 11. TRADITIONAL APPLICATION DESIGN
  12. 12. APPLYING DOMAIN DRIVEN DESIGN
  13. 13. STRATEGY #1: ONE DB PER MICROSERVICE
  14. 14. STRATEGY #2: VIRTUALIZATION
  15. 15. CACHING: REDUCING LATENCY FOR MICROSERVICES
  16. 16. ▪ ▪ ▪ ▪ DEPLOYING HA APPLICATIONS ON OPENSHIFT
  17. 17. ● ○ ● ○ ● ○ ● DEPLOYING HA APPLICATIONS ON OPENSHIFT
  18. 18. ▪ ▪ ▪ ▪ ▪ STATEFUL HA APPLICATIONS ON OPENSHIFT
  19. 19. ▪ ▪ ▪ ▪ ▪ Cross-data center high availability (HA) with OpenShift
  20. 20. STORAGE REPLICATION STRATEGIES
  21. 21. STORAGE REPLICATION STRATEGIES
  22. 22. COLD STANDBY WARM STANDBY DISASTER RECOVERY APPROACHES
  23. 23. HOT STANDBY HOT STANDBY, READ REPLICAS DISASTER RECOVERY APPROACHES
  24. 24. ACTIVE-ACTIVE DISASTER RECOVERY APPROACHES
  25. 25. Access and Protect SQL Databases in Microservices Applications HOW DOES NUODB HELP DEPLOY THESE DATA STRATEGIES INSIDE OF OPENSHIFT
  26. 26. TRADITIONAL DATABASE DEPLOYMENT PITFALLS
  27. 27. EACH IS A SQUARE PEG... ▪ ▪ ▪ ▪ ▪
  28. 28. NuoDB IS DEPLOYMENT AGNOSTIC ▪
  29. 29. CONTAINER-NATIVE SQL DATABASE + ▪ ▪ ▪ • • + ▪ ▪ ▪
  30. 30. Copyright © 2018 NuoDBCopyright © 2018 NuoDB CONTAINER NATIVE - IN-Memory Cache Container Native DB ` TE TE TE TE TE TESM SM + + + +
  31. 31. AUTOMATIC HA & DR / ACTIVE-ACTIVE + + + + TE TE SMSM TE TE SMSM
  32. 32. Copyright © 2018 NuoDBCopyright © 2018 NuoDB ELASTIC SCALE IN + OUT + + + + + + + + +
  33. 33. CD/CI PIPELINE INTEGRATION + ▪ ▪ +
  34. 34. AUTOMATED OPERATIONS + ▪ + +
  35. 35. NuoDB “inside” OpenShift
  36. 36. Copyright © 2018 NuoDBCopyright © 2018 NuoDB LEARN MORE ABOUT Red Hat and NuoDB at: THANK YOU

×