SOA and CRUD
There is complete census that CRUD is Anti-SOA pattern
Simon thinks that one can think of CRUD as business events rather than service operations
Maarten Mullender’s says to take the best of both worlds. Use CRUD interfaces for service when concurrent updates can be avoided because
1. Updates are seldom, or
2. Updates have only one source (person or system)
Ramkumar Kothandaraman writes
If one of the services fails to handle the CRUD request, then the EA service should be able to handle this business exception. One of the mechanisms to handle a business exception involves executing a flow that compensates for prior activities.
A Business Analyst usually determines Compensation Logic. Compensation Logic can be either automated or manual. For example, a compensation action may involve alerting the monitoring facility when one of the services returns a business exception, leading to a manual resolution.
There are going to be CRUD operation even for a SOA scoped Application. Best way of writing optimum CRUD operations is to visualizing a client talking to a service rather than a traditional RPC application.
Service APIs will be designed or dictated by client application and it is responsibilty of client to submit bulk CRUD operation with concise payload. It is responsibility of client to make sure that it has correct state.
Refactoring is a disciplined technique of making changes to software code structure, altering its internal structure without affecting its ...
Survic has very nicely argued that database storage and retrieval is 80% ( I would say 70%) portion of application. Mocks ups, Screen Desig...
Architecture - client requires at least rudimentary skills in these areas. What is SOA? Benefits? SOA principles for WS? Name standard arc...
Petshop Architecture 4.0 I have used earlier Petshop Architecture. It left a mixed feeling. It was simple to start with but not extensible...