tlandeka

5 ms·

1.
by tlandeka 4y ago
I followed the examples from the books. But let's say, my idea is to use that "boilerplate" code on other projects and not broke the DRY principle, I would rather extract that piece of code to be reusable.
2.
by tlandeka 4y ago
"domain" is real domain that contains business logic, "ddd" should be extracted to a common library (according to this example https://github.com/VaughnVernon/IDDD_Samples/tree/master/
3.
by tlandeka 4y ago
Q: there are imports for Spring in the domain code (is Spring part of your domain?) A: At only one place in order to be easy to replace it. I followed Vaugh Vernon example of mixing it: https://github.com/VaughnVernon/I
4.
Domain-Driven Design – art of writing a good code (production ready example)(github.com)
11 points by tlandeka 4y ago|6 comments
5.
Microservice for Authentication with Domain Driven Design and CQRS(github.com)
2 points by tlandeka 4y ago|0 comments
6.
by tlandeka 4y ago
This is not another proof of concept (PoC). The goal is to present the implementation of an application that would be ready to run in production.
7.
SpringBoot Microservice with Domain Driven Design and CQRD(github.com)
1 points by tlandeka 4y ago|1 comments
8.
Microservice for Authentication with Domain-Driven Design(github.com)
2 points by tlandeka 4y ago|1 comments
9.
by tlandeka 4y ago
Full Spring Boot authentication microservice with Domain-Driven Design approach with CQRS. This is not another proof of concept (PoC). The goal is to present the implementation of an application that would be ready to run in production.