After careful deliberation, we’re finally able to reveal #macroservices. More details at macroservices.org

May 6, 2020 · 1:50 PM UTC

20
75
10
233
Replying to @stilkov
Do I need a licence to use macroservices? How do I pay you?
4
Replying to @stilkov
What’s next? Monoservice?
1
Replying to @stilkov
I feel a little sad on how much I agree with your approach because it makes me realize how effectively the term „microservice“ has been misinterpreted (not to say misused) and finally got destroyed... so yeah, let’s start a new hypecycle 😉
1
Replying to @stilkov
Plus ca change.
3
Replying to @stilkov
That's Rick-Rolling INNOQ style :D
14
Replying to @stilkov
360 degree to a .WAR file ...
1
Replying to @stilkov
Been pushing this for years to deaf ears!
1
Replying to @stilkov
The industry attempts to neologise this pattern will be fun
1
Replying to @stilkov
Let's consider UI as a separate project. May expert users like to contract each systems independently but for many usual users, most of the subsystems are just one. It's the reason gateways and api compositions exists.
Replying to @stilkov
Brilliant and to the point explanation. Sums up the last 10+ years of defining microservices, bounded contexts, service mash-ups and so on in an easily understood and comprehensible manner. Good job!
2