If you want to get first hand infor­ma­tion about Apache Sling, make sure to attend this year’s edi­tion of adaptTo() in Berlin. I’m really look­ing for­ward to this event. This year I’ll present a tour through the mile­stones of Apache Sling dur­ing the last 12 months. So learn what’s hap­pened and join for look­ing into the poten­tial future of Sling and the inno­va­tions to come in the next months. This year, we’ll cover a lot of dif­fer­ent excit­ing new top­ics with some sneak peaks.

One major new fea­ture of this year is the new dis­cov­ery mod­ule which allows to describe topolo­gies of instances, rang­ing from clus­tered instal­la­tions to more het­eroge­nous topolo­gies. For the first time, this new API give’s the pos­si­bil­ity to intro­spect the topol­ogy and make use if it. I’ll present this new fea­ture together with the new improved job han­dling of Sling which uses the new topol­ogy information.

The OSGi event admin by design is an ad-hoc publish-subscribe deliv­ery mech­a­nism which gives you now guar­an­tee of deliv­ery or pro­cess­ing. In addi­tion, it has no sup­port for instance to instance mes­sag­ing. Sling’s event­ing mod­ule adds all the­ses fea­tures and sup­ports pro­cess­ing of mes­sages exactly once. Pow­ered by the new dis­cov­ery mod­ule, the improved job han­dling can dis­trib­ute job exe­cu­tion in a clus­ter or more advanced instal­la­tion sce­nar­ios. I’ll cover all of the above in my talk, explain­ing all the details about the job handling.

But these are just two ses­sions for adaptTo() — check out the web site for all the great stuff hap­pen­ing and be there to meet the community.