Fair deal, I'd say. Only problem is that most of the applications are from vendors, so getting problems fixed is an ordeal.
Every project I worked on, developers (consultants like me) advocated for finding a way of bypassing the hosting partner, and either doing their thing on top of platforms like Hetzner, or switching to AWS/Azure. Not because they particularly love AWS, but because the default hosting solution sucks so much arse.
I can totally see EU cloud infrastructure working for the public sector, but ONLY if they come with the same level of self-service management as the big cloud providers. Without that, it's a non-starter.
[1] One of those is a large French company on the verge of banruptcy.
https://www.marines.mil/News/News-Display/Article/500002/mar...
- In domain-driven design, the Domain layer is one of the common layers in an object-oriented multi-layered architecture.
- DDD is against the idea of having a single unified model; instead it divides a large system into bounded contexts, each of which have their own model.
I do not know what these mean and I have found no real good explanations. In my 20+ years of experience I have not seen any problem which is solved elegantly with DDD based development and/or CQRS etc.
My simple rule of new tech / random things such is these is - what is the adoption rate and what are the major success stories. With technologies like RoR, React, Spring Boot, Kotlin etc. it is easy to see the reason for their adoption and success. I have heard no such stories for DDD. In fact, I have found the developers which advocate these have been the hardest to work with (rich on theory and opinion and poor in actual written software).
If you have a large system it makes sense to divide it into smaller independent pieces. If you have a (micro)-service architecture you have distinct services, in a monolith you might have modules.
It is a hard problem to know where exactly the boundaries between services or modules should be, in any case DDD calls the things that make sense to decouple bounded contexts.
As far as I can tell, they're not related to the design pattern, but I never had to use that.