book VS IDDD_Samples

Repository

In chapter 2 of the Cosmic book, they talk about using Flask + SQLAlchemy in classic/imperative mode to enable the application of the dependency inversion principle (DIP).

I would recommend you using clean architecture. You can start with the cosmic book.

Continue with clean architecture in python

If you find this subject interesting, here is full implementation: https://github.com/jorzel/opentable/. I also recommend great book and code repository that was inspiration for writing this post: https://github.com/cosmicpython/book.

As the author, I encourage you to read it for free on github https://github.com/cosmicpython/book

Here is the direct link:https://github.com/VaughnVernon/IDDD_Samples/blob/master/iddd_collaboration/src/main/java/com/saasovation/collaboration/domain/model/forum/Discussion.java

"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/idd... and this one https://github.com/dddshelf/ddd)

Regarding to other issues, could you add little bit more concrete details just to check and consider possible solutions.

I try to apply DDD in my microservices, and will use a UUID generated by code as the primary key (based on how Vaughn Vernon defines a nextIdentity method in his repositories). That way, an entity always has an ID as soon as it is created. I don't need to persist it first in order for it to have an ID, and you can already identify the entity and use it in maps (since it has a hashcode generated solely by the ID), or you can publish domain events. Some nice benefits...

I would say this: link