Timeline for How to loosely couple modules in service oriented architecture
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2013 at 0:21 | comment | added | Andyz Smith | i tend to agree somewhat. What is the stated goal of the strategy to 'loosen' the systems? I'm all for architecture , planning and future proofing but you have to weigh those 'projected' benefits with the pain you feel right now trying to get richness between your subsystems. | |
| Oct 8, 2013 at 21:36 | answer | added | Alexey Zimarev | timeline score: 1 | |
| Aug 22, 2013 at 5:30 | answer | added | Edward Shen | timeline score: 1 | |
| Aug 21, 2013 at 15:05 | comment | added | Euphoric | Am I only one who thinks this "service-oriented architecture" is main problem and that with proper OOP design without premature abstractions, this would never happen? | |
| Aug 21, 2013 at 14:21 | answer | added | user53019 | timeline score: 3 | |
| Aug 21, 2013 at 13:07 | history | asked | Saeed Neamati | CC BY-SA 3.0 |