DB design for microservice architecture [closed]

by

Microservices offers decoupling. You must break down your application into independent domains. Each domain can have a DB. In case other MS needs to access data owned by some other microservices, they have to communicate over the network.

In case you feel that there are too many dependent services and the network calls would be too much, then you can define a domain, clustering the dependent services together.

For instance — Suppose I have an online Test evaluation Service where a manager of a company can post tests and he can view results of all the employees in his department.

My Microservices for this scenario would be:

Initial Design

  1. User Service: For login and user information.
  2. Test Service: Service to evaluate tests.
  3. Employee: Handles employee details
  4. Company: Handles organization CRUD
  5. Department: Handles department CRUD

After breaking it down, seems like employee, Organization and Department service would be making too much network/API calls as they are tightly dependent on each other. So it’s better to cluster them.

Updated design

  1. User Service : For login and user information.
  2. Test Service : Service to evaluate tests
  3. Organization : Handles Company, Employee and Department related operations.

Each service could have it’s own DB and it’s independently deployable. User and Test Service can use mongoDB or any NoSql DB and Organization service can use RDBMS.

Hope this helps.

More Related Contents:

  1. Microservices with shared database? using multiple ORM’s? [closed]
  2. Should each and every table have a primary key?
  3. Database, Table and Column Naming Conventions? [closed]
  4. What are the performance improvement of Sequential Guid over standard Guid? [closed]
  5. When and why are database joins expensive?
  6. Normalization: What does “repeating groups” mean?
  7. Copying data from one SQLite database to another
  8. Difference Between Firestore Set with {merge: true} and Update
  9. Can HTML5 databases and localStorage be shared across subdomains?
  10. What is a database transaction?
  11. Calculate distance between Zip Codes… AND users.
  12. Relational table naming convention [closed]
  13. When I should use one to one relationship?
  14. What’s the difference between findAndModify and update in MongoDB?
  15. PostgreSQL: Drop PostgreSQL database through command line [closed]
  16. How SID is different from Service name in Oracle tnsnames.ora
  17. Are foreign keys really necessary in a database design?
  18. Difference between a theta join, equijoin and natural join
  19. How to parse the data from Google Alerts?
  20. Database of common name aliases / nicknames of people
  21. Storing an image into an Attachment field in an Access database
  22. Best representation of an ordered list in a database?
  23. Business Logic: Database or Application Layer
  24. NULL permitted in Primary Key – why and in which DBMS?
  25. SQL LIKE operator in Cloud Firestore?
  26. Can I download an SQLite db on /sdcard and access it from my Android app?
  27. What are some best practices and “rules of thumb” for creating database indexes?
  28. Personal names in a global application: What to store [closed]
  29. CAP theorem – Availability and Partition Tolerance
  30. Database – Data Versioning [closed]

Leave a Comment