Timeline for Microservice architecture for multiple composite data entities
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2020 at 10:44 | vote | accept | vicky99 | ||
| Mar 29, 2019 at 9:00 | history | tweeted | twitter.com/StackSoftEng/status/1111553745219997696 | ||
| Mar 27, 2019 at 14:12 | history | reopened | Robert Harvey | ||
| Mar 27, 2019 at 13:52 | history | closed | Robert Harvey | Opinion-based | |
| Mar 27, 2019 at 13:51 | comment | added | Robert Harvey | You need to be clearer about what your actual goals are. "Correctness" is seldom a worthy goal all on its own. | |
| Mar 27, 2019 at 13:51 | answer | added | Michał Kosmulski | timeline score: 3 | |
| Mar 27, 2019 at 10:58 | comment | added | Neil | If a microservice must call another to work properly, then the release of a new update to one microservice may break another. This is what is supposed to be avoided. Microservices should be independent from one another. | |
| Mar 27, 2019 at 10:56 | comment | added | Neil | It can have common elements, but from a microservice standpoint, it must be self-sufficient entirely. On the webpage, the microservice should give you all the information you require without having to make additional calls to other microservices. It is purposefully meant to ensure that each microservice can follow its own independent development cycle (if a microservice requires some library with version A, and another with version A, then at any point a change can be made to version B and microservices only requiring A are still fine). | |
| Mar 27, 2019 at 10:50 | comment | added | vicky99 | Recommend service does not depend on other services. Its the other way round. Recommend service just provides recommended product ids. Next step is to call all other microservices to form the required objects. My question in this part is - are these kind of dependencies okay? Or there could be some better way to handle these dependent calls? | |
| Mar 27, 2019 at 8:55 | comment | added | Neil | "Some micro-service calls are dependent on others." It would not seem so based on what you've written. The issue seems to me that your Recommend microservice doesn't exactly fit the mold of a microservice, and the reason for this is that it is dependent on other microservices. If that isn't the problem, then please clarify. | |
| Mar 27, 2019 at 8:50 | comment | added | vicky99 | @Neil - I have purposely watered down my micro-services in this question to maintain focus on main question. All of our micro-services are independent and have good amount of complexity in them. | |
| Mar 27, 2019 at 8:04 | comment | added | Neil | My idea is that your microservices are too small. Each microservice should be entirely independent from one another and individually deployable. If they have elements in common, they should be implemented using a common library, if anything, but it would not be a microservice unless it directly contributed to a web page independently from the others. | |
| S Mar 27, 2019 at 7:19 | history | suggested | Engineert | CC BY-SA 4.0 |
Tags added, grammar improved and Thanks removed.
|
| Mar 27, 2019 at 7:17 | review | Suggested edits | |||
| S Mar 27, 2019 at 7:19 | |||||
| Mar 27, 2019 at 7:02 | review | First posts | |||
| Mar 27, 2019 at 13:52 | |||||
| Mar 27, 2019 at 6:49 | history | asked | vicky99 | CC BY-SA 4.0 |