Best approach to design a service oriented system
Posted
by Gustavo Paulillo
on Stack Overflow
See other posts from Stack Overflow
or by Gustavo Paulillo
Published on 2010-04-20T15:14:54Z
Indexed on
2010/04/20
15:23 UTC
Read the original article
Hit count: 303
Thinking about service orientation, our team are involved on new application designs. We consist in a group of 4 developers and a manager (that knows something about programming and distributed systems). Each one, having own opinion on service design. It consists in a distributed system: a user interface (web app) accessing the services in a dedicated server (inside the firewall), to obtain the business logic operations. So we got 2 main approachs that I list above :
Modular services
Having many modules, each one consisting of a service (WCF). Example: namespaces SystemX.DebtService, SystemX.CreditService, SystemX.SimulatorService
Unique service
All the business logic is centralized in a unique service. Example: SystemX.OperationService. The web app calls the same service for all operations.
In your opinion, whats the best? Or having another approach is better for this scenario?
© Stack Overflow or respective owner