Timeline for Application service layer calling database functions. Bad architecture?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2016 at 15:33 | comment | added | Greg Burghardt | No. The "S" in SOLID is the Single Responsibility Principal (SRP). But Separation of Concerns, which you are recommending, is a valid reason for separating service logic from data access logic. The other answer by Vladislav mentions the Single Responsibility Principal. Frankly, The SRP and Separation of Concerns go together well, like wine and cheese. | |
| Dec 7, 2016 at 15:30 | comment | added | J. Pichardo | Isn't it one of the solid principles? | |
| Dec 7, 2016 at 15:28 | comment | added | Greg Burghardt | Not sure why this was down-voted. This answer recommends separating code that deals with different concerns. Feels like a principal of programming here... not sure what it is... Man. If only I could think of the name. +1 BTW | |
| Dec 7, 2016 at 6:09 | history | answered | J. Pichardo | CC BY-SA 3.0 |