Modularize
From APIDesign
(Difference between revisions)
(New page: There are multiple correct ways how want to modularize your applications. How do you select the right one? This article provides you the best guidance you can get. == No Silver Bullet...) |
|||
| Line 1: | Line 1: | ||
| - | There are multiple correct ways | + | There are multiple correct ways to [[modularize]] your applications. How do you select the right one? This article provides you the best guidance you can get. |
== No Silver Bullet == | == No Silver Bullet == | ||
Revision as of 08:01, 23 October 2012
There are multiple correct ways to modularize your applications. How do you select the right one? This article provides you the best guidance you can get.
Contents |
No Silver Bullet
TBD: Andzrej's example.
The Modular Java SE Case
The Server Side
TBD: Do you want 14?
Driven by Need
The right granularity and even separation during architecting modular systems is driven by one's need. Primarily by the existing need, secondary by a future need that has to be estimated by envisioning the future evolution of the system.
Follow
