Cross-cutting issue. Or how not to miss that ASPECT when designing microservices

  • 20 min

Quickness of reaction and decision-making are no longer an advantage, but a necessary skill in our digitalisation times. And no, we’re not talking about corporate governance or strategic consulting; we’re talking about application architecture.

Flexibility, lightness, but, at the same time, high functionality and reliability are the cornerstones of a viable system that can address the challenges of tomorrow. Mistakes and “heavy decisions” waste valuable time of your project / product / service, forcing you to wallow in the abyss of endless unravelling the Gordian knot, instead of building up competitive advantages.

Have a look at this situation from the perspective of architecture design: let's pay attention to finding a place under the sun of your microservices for cross-cutting concerns, and also think about how aspect-oriented programming (AOP) can help an analyst or an architect anticipate actual challenges.

Comments ({{Comments.length}} )
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!