Todd Geist : Avoiding the Monolith


The traditional approach to solving the problem of code re-use has been for developer shops to build a monolithic framework and then squeeze all development into that framework. This leads to bloatware and encourages a one size fits all approach to building custom software, which makes no sense. A better solution would be to a have a collection of loosely coupled modules that could be assembled into solutions as needed. You only use what you need. Leave the rest out. Even pick and choose amongst different implementations.

In this session we will look at some examples of some loosely coupled modules, see how they can be assembled into a solution pretty quickly and then have a discussion about what we can do as a community to take it to the next level.

Subject Author Replies Views Last Message
No Comments