DDD Aggregate is responsible for encapsulating business logic for the component. But we need to be aware that when we are implementing business logic for a long time process that is coordinating many components, like subscription trial, we have another building block for this. It’s a process manager. Below I pointed out some differences between … Read more
In most cases, I use UUID as an id for aggregate entity. But when it comes to big amount of entities in SQL DB it can become scalability problem to handle UUID as id. Here are some pros and cons of different approaches to entity ids. Autoincrement Integer: DB 32-bit or 64-bit integer used as … Read more
Post in answer to a StackOverflow questions “SQLAlchemy and DDD” and “Persist POJOs in Python using a DDD approach”. You can find code used in this example here. DTO Having out DDD component I want to separation from DTO used by our aggregate and repository implementation. I introduce interface for DTO that will be delivered by … Read more
Post in answer to a StackOverflow question. You can find code used in this example here. Package structure In component package I use this modules as starting point. migrations/ app.py commands.py events.py exceptions.py repository.py service.py entity.py Commands A command is always DTO and as specific, as it can be from a domain perspective. I aim to create … Read more
