Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Design Goals

  • Single jar file. Ron W. Makes it hard to have collaboration, encourages intermodlue dependencies, makes build slow and test suite too big, makes it hard for developers to replace parts, makes it hard to support multiple lower level alternatives. Would prefer to have 8 separate projects with possibly different teams on some parts programming to agreed interfaces.

    Info
    iconfalse

    Ron, what you are describing is the current mess we are trying to fix. Consolidating the closely-coupled components into a single component (and jar file) is one of the main reasons for the rewrite - that is why it is first on the list of design goals.

  • Compact, small memory footprint.
  • Scalable from SBCs to enterprise-class ERP systems.
  • Reuses existing technologies.
  • Easy to configure and maintain.

    Note
    titleDesign Participants Note

    Please take some to watch this presentation by Joshua Bloch: How to Design a Good API & Why it Matters.

...