Timeline for Are there architecture smells?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2011 at 14:26 | comment | added | Klaim | That's why I added "no coupling at all often smells performance issues". I agree that you have to use coupling to enhance performance. It's when there is a lot of coupling everywhere (between the different modules/classes/whatever of your application) that there is an architectural problem. | |
| Feb 18, 2011 at 14:19 | comment | added | HLGEM | I have to disagree with that. If you are talking business applications, coupling to a database that is highly unlikely to change is smart not stupid. You can use the more performance feature that are database specific. | |
| Feb 18, 2011 at 14:16 | history | answered | Klaim | CC BY-SA 2.5 |