Timeline for What is one correct architecture when using a DB with multiple clients?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2011 at 15:18 | vote | accept | Stecy | ||
| May 16, 2011 at 15:18 | comment | added | Stecy | Yep, operations is the key word here ;) Thank you very much! | |
| May 16, 2011 at 15:00 | comment | added | Aaronaught | @Stecy: Try not to think of this in terms of methods and instead think in terms of operations. A single operation may support what you would logically define as several different methods. It isn't a problem for web service to have a lot of operations, but it is a bit of a design smell depending on the scope of your application. It's also generally good practice to separate web services by feature group; i.e. in a CRM you might have one service for sales, one for billing, another for financials, you get the picture. | |
| May 16, 2011 at 14:55 | comment | added | Stecy | I was not sure "turf it" meant "throw it away" but you confirmed it and it makes sense now. Effectively the web service is a thin wrapper. For that reason, we are going to replace it with a new web service that would provide domain methods to clients. However, in doing so the service will have a LOT of methods. Do you see this as a problem? Would it be more maintainable to have several web services? | |
| May 16, 2011 at 14:44 | comment | added | Aaronaught | @Stecy: It means throw it away. I get the impression that the service is just a thin wrapper over the database, which is worse than useless; if that impression is correct then I think you'd be better off not using it at all. | |
| May 16, 2011 at 14:31 | comment | added | Stecy | Please pardon my incomplete understanding of the english language but I'm not grasping the signification of the word TURF here. | |
| May 16, 2011 at 13:42 | comment | added | Aaronaught | @Stecy: Ah, the good old missing-source-code problem. Unless the existing API is filled with mysterious business logic, I would turf it - there's no productivity gain to be had in coding against a black-box service tier when you have white-box access to both the data and client tiers. | |
| May 16, 2011 at 11:47 | comment | added | Stecy | Thank you for the very detailed explanation. The web service is from a third party with no sources available so we will possibly replace it with an entirely new web service since we have control of the database. As of now the Web service is using an RPC-like interface so you're right this is heavily chatty. | |
| May 13, 2011 at 21:02 | history | edited | Aaronaught | CC BY-SA 3.0 | added 2 characters in body; added 6 characters in body |
| May 13, 2011 at 20:57 | history | answered | Aaronaught | CC BY-SA 3.0 |