I'm new to DDD.
From my current understanding and from the examples I've seen in books or articles, DDD addresses the design of a software system to solve a complete domain problem.
So it figures out the domain models, use ubiquitous languages for communication between domain experts and software developers, find out bounded context and separate to sub-systems like aggregates, and a lot more.
DDD concepts are also quite useful during the move from a monolithic system to multiple microservices.
However, in a company, we collaborate as different teams to deliver a complete system. We only work in a team that is only responsible for a component in the system. The component can be a program or a microservice. It only participates in a very small part of the whole domain solution. Maybe it is just a ENTITY in the DDD concept. Even worse, if the component is in the infrastructure layer, it won't have a corresponding mapping to domain object at all.
My question is, in this case, if I own just a component in the whole system, is DDD still useful to me?