Timeline for Communication in a microservices architecture with flask and REST
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 6, 2018 at 22:11 | vote | accept | Shahlin Ibrahim | ||
| Dec 6, 2018 at 6:03 | comment | added | Shahlin Ibrahim | This is the how I'm planning on solving the issue. Have one service called Room Design which contains two packages or libraries - Furniture Selection and Furniture Placement. This way they're still separate packages and can be independently developed but can also be put together using the Room Design Microservices | |
| Dec 5, 2018 at 19:59 | comment | added | Paul | No, I'm saying that not everything needs to be the smallest possible microservice. Microservices should be logical chunks of work, which might mean that they do more than one thing under the hood (in your programming language of choice). If nothing else talks to the Furniture Placement service except the Furniture Selection service, then you don't need them to both be web-accessible services. Even if other things need to talk to both, it might make more sense to expose them as different API calls on the same service. | |
| Dec 5, 2018 at 19:38 | comment | added | Shahlin Ibrahim | Are you saying, have a Room Design microservice which communicates with the two algorithm services and composes the response and sends it to the API Gateway? | |
| Dec 5, 2018 at 19:26 | comment | added | Paul | @ShahlinIbrahim that is much better thank you. Interestingly enough, one of my first freelance jobs was for a bespoke furniture company in the UK. :) | |
| Dec 5, 2018 at 19:25 | history | edited | Paul | CC BY-SA 4.0 |
added 1156 characters in body
|
| Dec 5, 2018 at 19:16 | comment | added | Shahlin Ibrahim | I have edited the question and added an example of the business problem | |
| Dec 5, 2018 at 18:26 | comment | added | Paul | @ShahlinIbrahim There are very few objectively "bad designs" in my opinion. There may be designs which better suit certain requirements than others, so it's hard to say without knowing what you're actually doing. That said, having a Gateway that composes an API response from several microservices is not uncommon, it's just not the best thing in all situations. Tell us more about your actual business problem and I can give better advice. | |
| Dec 5, 2018 at 16:29 | comment | added | Shahlin Ibrahim | Your third paragraph, that's what I meant. Although is it really okay if the API Gateway sends requests to multiple APIs synchronously? Or is that bad design? | |
| Dec 5, 2018 at 15:11 | history | answered | Paul | CC BY-SA 4.0 |