Locations of visitors to this page

Antidoto - The architecture-two-dot-oh

Antídoto is the portuguese word for antidote. An antidote is a substance which can counteract a form of poisoning.

Antidoto is a java technology mashup enabling modularization for Java enterprise technologies such as Spring and Hibernate. Modern java technologies are component based, but lack modularization capabilities. Here is where the poisoning is happening and where Antidoto jumps in. To enable modularization, Antidoto defines a simple module metamodel, where a system represents the whole and subsystems are the composing parts. As such Antidoto defines a coarse grained component model. We prefer subsystem over component as the latter term is being used by many frameworks to describe fine grained components. By providing building blocks for modular architectures, Antidoto forms a thin modularization layer ontop of well known Java technologies.

What for?

Antidoto is a technology mashup - it does not reinvent the wheel. Some of the core improvements offered by Antidoto are:

  • dynamic loading of dependent subsystems (with recursion) by reading the dependencies declared in maven2.
  • framework for distributing logging configuration for log4J across subsystems
  • framework for distributing hibernate configuration across subsystems
  • framework for distributing JSF and Facelets related configuration and artifacts across subsystems
  • simple priorization levels for beans in Spring context

    ... and more to come!

What next?

Antido consists of a set of subsystems providing some very simple solutions for problems emerging with modularization.

Have a look at the documentation of the available substems: