Until recently the work was supported by essentially monolithic projects, but recently we got a order for a new big project.
Once it was decided to do everything on the RESTFul microservices with Docker. Database - Postgres
The Micro Service And
A Micro Service In
Broker event with different event processing
There is a problem - the arm includes a bunch of pivot tables with different microservices, with filters, sorting and so on. and so. of the services and
Because of this, in the micro service In wound in DB reference to some entity A, so it is possible to build foreign keys.
If the number of microservices with the interactions starts to grow, this will result in a huge number of directories in each micro service + same model with the logic for CRUD
The front may not be the one to filter, as there is a pagination and sampling filters must lie on the database.
I would be grateful if anyone can help and better advise a book to read.
All guides can be identified in a separate micro service, for example. And even when a large volume of related resources should have to look at graphQL
maye.Hansen8 answered on March 23rd 20 at 19:08
The service needs a directory service receives it via the rest api, or to the processing of data come with all you need and it spits back the result. What about integrity outside of the scope of micro service, micro service a little worried(I'm about the keys). To make the data easier to drive, invented by different protobuf. For the front is way too protobuf, it is better this way to watch, not graphql/json api/soap, etc. and the microservices is a separate pain in the ass if you have a small team, it is in this sense precisely zero.
macie answered on March 23rd 20 at 19:10
You are the problem nicely decide without denormalization and data duplication. The only option in a separate micro service summary tables to highlight, to pour the data and to pull them out via the API otherwise on the front of the engine, the OLAP have to be washed down.