Below is just an example. Your client side may have different architecture. Using these component services a transaction is built. And the whole development code is isolated from each other and have a specific purpose. Example - D service will have all the reads, create, update, delete statements on entities. So during maintenance it needs to be touched only if affected database is changed.
Types -
H Service - Test Harness. To test the transaction
I Service - Interface. It is a Public Operation – the interface to the service
M Service - Private Operation Manager – the director or traffic cop
C Service - Contains isolated logic. e.g. editing of imports or doing calculations, client side
T Service - Translator: Transient view to Persistent view
D Service - Data Access – goes against the database
P Service - Translator: Persistent view to Transient view
X Service - External Wrapper – an EAB that interfaces with an existing program
S Service - Error Processor – translates Exit States to Return Codes
No comments:
Post a Comment