Timeline for How to replace parallel async calls between micro services with event based communication
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2018 at 22:58 | comment | added | amon | @RobertHarvey it's good that costs are more well-known because that prevents hype driven development. While I personally think MSes tend to be over-applied, it's undoubtedly a viable architecture for many applications. Some critical pieces (such as wide availability and reliability of Kubernetes) are slowly falling into place. Looking at the hype cycle, I'd argue that the industry is currently at the verge of the “plateau of productivity”, whereas some individuals still have to get past their “peak of inflated expectations”. | |
| Nov 15, 2018 at 17:22 | comment | added | Telastyn | @RobertHarvey - personally, I tend to think they are for most scenarios (though certainly not all). You need to decompose software to make it vaguely maintainable and flexible. Having a clear separation between parts helps prevent the messy implicit coupling inherent in the worst of software. And the usual cost (someone needs to actually automate deployments, we need to actually figure out how to correlate distributed log messages, we need to figure out how to package shared code) are things that engineers need to do anyways. | |
| Nov 15, 2018 at 15:50 | comment | added | Robert Harvey | Increasingly, I keep hearing about the costs of doing microservices. Are they worth the trouble, in most scenarios? | |
| Nov 15, 2018 at 6:09 | history | answered | Telastyn | CC BY-SA 4.0 |