The document discusses the importance of modularity in software architecture, emphasizing its role in coping with complexity and facilitating agile development. It advocates for the use of existing solutions like OSGi for dynamic modules and highlights examples such as chat applications and ad generation services. Ultimately, the author encourages demonstrating practical implementations rather than just discussing theoretical concepts.

1. What’s Up with
Modularity ?!

2. Paul Bakker
@pbakker

3. Observations
Extremely agile
(first mover advantage)
Architecture (and code base)
should be able to cope with change
Trend
Applications tend to
grow bigger and more
complex
Agile development
and refactoring have
become more common

4. Modularity
is the answer

5. What we lear ned about OO design in university :
Prevent
(tight)
coupling
Promote
cohesion
cohesion
coupling

6. Modules Service Lookups

7. What do we need
design
consequences
High-level
enterprise APIs
Architectural
focus on
modularity
Runtime
dynamic
module
framework
Right now,
OSGi is the
only option
let’s not
reinvent the
wheel
for modularity?

8. Stop talking…
and show me code!

9. Demo

10. Rooms
Resource
AngularJS
Client
Rooms Service
RabbitMQ
RabbitMQ
Service
STOMP
WhatsUp
Architecture
AMQP
Chat Log
Jongo
Mongo
REST

11. Rooms
Resource
AngularJS
Client
Rooms Service
RabbitMQ
RabbitMQ
Service
STOMP
$$$$$$$$
AMQP
Word Counter
Chat Log
Jongo
Mongose
REST
Yeah baby!
Personalized
Ad Generator
$$$$$
Product
Service
MongoDB
$$$$

12. Demo

13. Wrap up

15. Eclipse OSGi plugin
http://bndtools.org/
Open source
OSGi components
http://www.amdatu.org/
Amdatu
That’s us
http://luminis-technologies.
com
Paul Bakker
paul.bakker@luminis.eu
@pbakker