Use case depends on another use case
I have below use cases:
Need help on Clean Architecture with Service/Manager/Controller
i am developing an android application trying to comply with Uncle Bob’s clean architecture.
what specific needs of a project should i be considering when creating an architecture model for my project?
i am at the very beginning stages of developing a hybrid project, and am at a bit of a loss when it comes to deciding what kind of structural method to use. all of the advice I’ve read on the subject basically states that there is no one size fits all, and what matters most is your app’s core functionality and team’s need.
Entity in clean architecture. How is structured the entity layer of the clean architecture?
In clean architecture, should the entities in the entity layer interact with each other like in a class diagram or can they be independent of each other ?
Typescript Clean Architecture: How to tackle use case that needs multiple repositories?
I am implementing clean architecture in my new back-end project and getting stuck with a particular use case.
What value does the mediator pattern add beyond dependency injection?
Does the mediator pattern add any value beyond dependency injection? I am encountering the mediator pattern for the first time in context of this sample application, which is meant to demonstrate how to follow Clean Architecture in .NET. I assume this pattern was included so it wouldn’t be too distracting for devs who expect it to be used; but it wasn’t the main focus of the sample code, or the book that this code accompanies.
How handle foreign keys in bounded contexts inside a monolith?
in my company we have a Django monolithic application. To be clear, we are not looking into moving to micro-services. For the past few months, I have reading and implementing a DDD architecture inside the monolith, trying to setup the django modules as isolated as possible from the rest of the application. I have somehow successfully done this, except for the testing part.
CQRS: Multiple entry points for a single command
I’m trying to follow the Clean Architecture and CQRS within an application that, let’s say, create a product.
CQRS: Multiple entry points for a single command
I’m trying to follow the Clean Architecture and CQRS within an application that, let’s say, create a product.
Can the application layer extend the domain models?
I write BFF (Backend For Frontend) and it’s domain is to provide user info and microservices integration.