Timeline for Microservices: MonolithFirst?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 18, 2021 at 5:17 | history | edited | lennon310 | CC BY-SA 4.0 | typo: *threatens, *your; link added to python for edit least limitation |
| S Jan 18, 2021 at 5:17 | history | suggested | Yami Odymel | CC BY-SA 4.0 | typo: *threatens, *your; link added to python for edit least limitation |
| Jan 18, 2021 at 4:51 | review | Suggested edits | |||
| S Jan 18, 2021 at 5:17 | |||||
| Apr 23, 2018 at 13:57 | comment | added | Christian Sauer | @Walfrat I tend to agree, but the temptation to reuse existing code is much greater (and less easily squashed) in a monolith. E.g. "oh look, somebody defined an WidgetId, I will just reuse that for my FormId": Also, you cannot easily use another language / db for a project, which really fosters the "everybody must use common tools" thinking | |
| Apr 23, 2018 at 13:32 | comment | added | Walfrat | While I agree with your first sentence, I think you should consider that even your monolith should already be "modular-like" inside, otherwise you just won't be able to separate anything without having everything falling. | |
| Apr 23, 2018 at 12:40 | comment | added | Christian Sauer | @amon Thank you, I have corrected the sentence - my son did interrupt me 34235 times so I was confused ;) | |
| Apr 23, 2018 at 12:39 | history | edited | Christian Sauer | CC BY-SA 3.0 | deleted 4 characters in body |
| Apr 23, 2018 at 12:14 | comment | added | amon | “and in such cases a microservice can be easier to develop” – did you mean to talk about monoliths there? | |
| Apr 23, 2018 at 5:10 | history | answered | Christian Sauer | CC BY-SA 3.0 |