Date

12 Jan 2018

Attendees

Goals

Watch learning material Clean architecture: Patterns, Practices and Principles:
- Domain-centric Architecture
- Application Layer
- Microservices

Discussion

Packages in our services (flat, not feature-based, may not be very clean)
Could we use application layer and command pattern to better wire business/domain logic and Spring beans?
Would there be any use of introducing commands/queries and separate write/read databases? (Possibly a lot of effort)
Pros & cons of microservices
How to properly model actions like submit / approve / finalize? And would we ideally want to replace such action endpoints with strictly RESTful operations

Wrap up

We have asked every participant to give a score on how useful this meeting was and how helpful this specific material was. The voting was anonymous and each participant could give a score from 1 (useless) to 10 (very useful).
The averages were:

How useful are those meetings:
How useful was this specific material:

Action items

Mateusz Kwiatkowski to review and follow up on "How to properly model actions like submit / approve / finalize? And would we ideally want to replace such action endpoints with strictly RESTful operations?"
Paweł Albecki (Deactivated) to review and follow up on packages in our microservices and recommendation for naming/nesting packages
Łukasz Lewczyński (Deactivated) to review and follow up on "Could we use application layer and command pattern to better wire business/domain logic and Spring beans"