News for hackers. Stuff that matters.
Re:Microservices – architecture nihilism in minimalism's clo... by UK-Al05 on Tuesday November 03, 2020 @05:52AM (#24978396)
That's microservices.
Re:Microservices – architecture nihilism in minimalism's clo... by oblio on Tuesday November 03, 2020 @08:53AM (#24979639)
That's services. And Service Oriented Architecture, circa 2000.
Re:Microservices – architecture nihilism in minimalism's clo... by UK-Al05 on Tuesday November 03, 2020 @09:07AM (#24979745)
Indeed. According to Sam Newman, the main difference smart pipes/dumb pipes.

SOA has ESBs. But both are built around bounded contexts.

Calling them "micro" was a bit of mistake.

Re:Microservices – architecture nihilism in minimalism's clo... by balfirevic on Tuesday November 03, 2020 @08:30AM (#24979439)
Are we just adding prefixes to words for fun?
Re:Microservices – architecture nihilism in minimalism's clo... by UK-Al05 on Tuesday November 03, 2020 @09:08AM (#24979751)
Pretty much yeah.
Re:Microservices – architecture nihilism in minimalism's clo... by yonixw on Tuesday November 03, 2020 @07:17AM (#24978933)
Naïve microservices are separated per data store\DB. Because DBs are usually the bottleneck and we want to scale them separately per usage. Looks like they combined some to make it possible to manage, while not utilizing resources to the max.
Re:Microservices – architecture nihilism in minimalism's clo... by UK-Al05 on Tuesday November 03, 2020 @07:58AM (#24979200)
The requirement of transactional consistency is one of the ways you identify a bounded domain in DDD. Well aggregates at least.

If you require transaction consistency across multiple microservices. They are to small.

If you don't require transactional consistency across microservices that's ok. Therefor they can be in separate databases anyway and messaging can be used.