Timeline for Microservices with OOP and Functional Programming
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2018 at 15:01 | comment | added | Robert Bräutigam | I'm saying barring any other factors/requirements, there should not be a "mobile API" service. That would need synchronous request-response communication with the "chat service". This couples both, and makes the whole construct more fragile. The "chat service" itself should support a mobile-consumable interface for its own chat-related things. | |
| Mar 21, 2018 at 13:58 | review | Suggested edits | |||
| Mar 21, 2018 at 14:55 | |||||
| Mar 21, 2018 at 13:40 | comment | added | DaAmidza | Thanks a lot for clarifying some things.When you said that microservices should not communicate with each other did you mean in the sense of child-child or child-parent?Let's say Facebook parent mobile API has the child chat microservice.And the communication with the phones goes over the parent than to the child microservice.Id likes to clarify this than I'll accept the answer. | |
| Mar 21, 2018 at 13:25 | history | edited | Robert Bräutigam | CC BY-SA 3.0 |
added 399 characters in body
|
| Mar 21, 2018 at 13:19 | history | answered | Robert Bräutigam | CC BY-SA 3.0 |