My understanding is the query module it is a collection of database views keeping together information from module A and module B databases. Probably module A and module B databases are exposed each by their own application that read and write the database.

query module reads it gathers the data from different services (calling their Rest end points)

The architecture it is already a service oriented architecture (SOA). It might seem a monolith by having all the applications packaged in a sole package, a side useful to detail: why it is a monolith when the communication between modules it is performed over HTTP. To understand where it can get to consider each method from the application's code could be exposed through its own REST end point and its direct calls replaced by calls over HTTP/HTTPS. With that type of setup from a certain stage the development burden gets replaced by the administrative one that in the end fades out also transferring the burden to the infrastructure that in case of under development private clouds could get unmanageable a down side the popular public clouds has overtaken. Therefore I think there are two questions (1) for short/medium term "what is the time span the development could be a tolerable bottleneck?" and (2) for long term "what resources the business side can invest in the infrastructure?" rephrased that would be "what it is the cost of infrastructure the business side could support on long term?".

My understanding is the query module it is a collection of database views keeping together information from module A and module B databases. Probably module A and module B databases are exposed each by their own application that reads and writes the database.

query module reads it gathers the data from different services (calling their Rest end points)

The architecture it is already a service oriented architecture (SOA). It might seem a monolith by having all the applications packaged in a sole package, a side useful to detail: why it is a monolith when the communication between modules it is performed over HTTP. To understand where it can get to consider each method from the application's code could be exposed through its own REST end point and its direct calls replaced by calls over HTTP/HTTPS. With that type of setup from a certain stage the development burden gets replaced by the administrative one that in the end fades out also transferring the burden to the infrastructure that in case of under development private clouds could get unmanageable down side the popular public clouds has overtaken. Therefore I think there are two questions (1) for short/medium term "what is the time span the development could be a tolerable bottleneck for the business?" and (2) for long term "what resources the business side can invest in the infrastructure?" rephrased that would be "what it is the cost of infrastructure the business side could support on long term?".