CEO/Principal Consultant at INNOQ, he/him, software architect, RESTafarian, conference tourist. Works at innoq.com. Fediverse: @stilkov@innoq.social

Germany
Joined April 2007
Filter
Exclude
Time range
-
Near
The point, to me, is to allow for independent evolution of parts
Despite being a cool platform, Lambda is just one potential choice. How will I move to the next thing in five years?
Replying to @adrianco
Definitely the future model in terms of infrastructure support, I won’t disagree. I still think a larger “unit” is needed, too
4
Even as a proponent of what I perceive to be the core concepts of microservices, I think building hundreds of very small ones is a bad idea
8
31
1
45
"This is the most dangerous time for our planet" – Stephen Hawking theguardian.com/commentisfre…
18
1
16
Replying to @jkuipers @ewolff
Similar to how you can just build a modular monolith: True, but a technical boundary helps
1
Replying to @ewolff
Unsurprisingly, we agree. I just meant to say that many existing microservices architectures miss this point.
2
1
Replying to @ewolff
Inseparable: If database schemas are shared, development and deployment need to be synchronized every time there's a schema change
4
1
1
Replying to @mivesto
Completely undisputed – far easier up to a certain size (though I do wonder why people split them up in the first place, then)
1
I don't think they are, but I think they should be
Maybe separated databases are the core of Microservices like architectures.
4
2
6
Things you’ll only ever read in US newspapers: “two family guns were missing” washingtonpost.com/news/morn…
1
1
Hier der Code für die Fehlerbehandung (/cc @ewolff)
2
4
6
For the same reason, an SCS could be composed of a hundred fine-grained microservices
… that does not mean all of its parts have to deployed as one unit.
I think you’re missing the point: It’s key that no DB is shared between two SCSs …
1
Doesn't have to be a single unit, but an SCS is always deployable separately from others
1
While an SCS can consist of multiple deployment units, the reverse is never the case
1
Microservices and SCSs don’t treat deployment boundaries as an implementation detail.
2