Angie: ejabberd roadmap updated

We have recently updated ejabberd roadmap on our support site. The roadmap is itself a work in progress, but give a nice overview of what you can expect for ejabberd in the short term.

The Angie program will be split into four releases. Each of this release introduces a major architectural change and adds many new end-user features.

• ejabberd 2.0: This version introduces a new architecture, called Flexarch. The basic idea is to have the most flexible and configurable architecture to adapt to every organisation deployment requirements without pain. Flexarch will be described in a future post. This release is expected to reach beta state at the end of may 2007 and should be ready for production before july 2007. This version will also add many end-users features such as PEP, proxy65 support for file transfers and many more additions that we will describe in other blog posts. This version also brings large improvements for enterprise-grade LDAP support.
• ejabberd 2.1: This version is expected to change the relational database architecture support to make it more flexible and ease code maintenance.
• ejabberd 2.2: This version will be a major optimisation of the code base and will dramatically improve the performance and the memory consumption. It will integrate a new XMPP parsing library called exmpp, common to ejabberd and Jabberlang. More on this new library soon, which is the key of this performance boost.
• ejabberd 2.3: This version will improve the consistency of the cluster configuration mechanisms. A single configuration file describing the complete cluster will be introduced, radically improving cluster management.

The roadmap is still evolving and you are of course very welcome to get involved with us. Contributions, suggestions are very welcome !

References

• Angie: Millions Users Instant Messaging
• Angie: Building Large Scale AJAX Chat System

Comments

Is version 2.1 expected to allow flexible database layout like custom fields or many virtual domains in one database?

Will it allow keeping all information in SQL database, so Mnesia database engine will be optional?

Posted by psz on 21 May 2007 at 17:00

Hello Patrick,

The exact scope of the version is not totally defined. We have focused on defining thema to work on.

We did not thought about adding this kind of flexibility, but this is a good idea. We will try to integrate those features in the roadmap for 2.1.

Regarding SQL database, you can already store everything into the relational database. The only remaining thing in Mnesia as of today is the MUC room configuration.
However, Mnesia will still be use for keeping transactional in memory states.

Thank you for your feedback !

Posted by Mickaël Rémond on 22 May 2007 at 16:46

Hello,

Is there a new roadmap to ejabber 2.0?

Thanks

Posted by Pepe on 24 Sep 2007 at 08:51

Yes, it will be in beta in october 2007.

Posted by Mickaël Rémond on 24 Sep 2007 at 08:56

Add comment