I have been read many architectures such as N-Layered, Onion ,... . But I'm designing a large system that is working by some huge databases and provides a lots of services to another applications/clients.
in the other hand our system have to be designed very extensible. the parts of our system that named modules or subsystems, have own models,Business logic and maybe own Uis or services. even some modules don't have any UI nor any services to serving out of systems, these modules just extends our system.
I'm a member of designer team and I'm thinking about the below architecture for our system:
it is onion architecture, but the entities of database defined in every modules.every modules will develop by a separate team. we don't have dependency between them. but our database is single!
one of my concerns is this, how can they dependent each other? is right architecture for us? if is, what are the other concerns? if no, what architecture(s) you suggest?
Aucun commentaire:
Enregistrer un commentaire