Accessing Data Across Modules v2

[hellloy]

How can I access and work with data stored in a table from another module while staying within the framework of the current architecture? For example, if I need to use data from the ToDo Service module while working in the Catalog Service module, what is the recommended approach for accessing and integrating that data between different modules?

Additionally, how should I handle situations where relationships between domain models in one module reference models from another module? What is the best way to manage these cross-module dependencies while adhering to architectural principles?

Thank You !

[kallievz]

Hi Hellloy.
I am sitting with the same issue, also not sure which will fit and adhere to the architecture. There is several options available, and all have listed pro's and con's. I am also waiting for same as how to follow @iammukeshm flow.

I ideally would like to create a db where all "master" data will live, eg. Lookups etc that will be static data, and would not change, as business logic in both DB and Code would be built around it. So altering this "static" data would be a calculated decision.

Please see article that will explain :
https://medium.com/@john_freeman/querying-data-across-microservices-8d7a4667668a

[hellloy]

Hi @kallievz !

Thank you for your response! Your idea of creating a separate database for storing master data, such as lookups and static information, sounds logical and has its advantages. Centralized management of data and minimizing duplication, especially in the context of microservices architecture, seems like a solid approach.

I fully agree that any changes to such data need to be carefully considered, given their impact on business logic. This definitely seems like a reliable solution to consider.