What bet­ter way to start the new year than with a glimpse of what the fu­ture will bring for Java?

Another great in­de­pen­dent ar­ti­cle on how the app serv­er is dis­ap­pear­ing, with the ESB go­ing along:

Mi­croser­vices are all about split­ting up re­spon­si­bil­i­ties of your do­main's bound­ed con­text into sev­er­al HTTP-like ser­vices, de­ployed in­de­pen­dent­ly. So es­sen­tial­ly it means split­ting up process bound­aries across dif­fer­ent ser­vices - away from the mono­lith...

Scal­ing ap­pli­ca­tions to the web and the cloud - com­bined with con­tin­u­ous de­ploy­ment au­toma­tion prac­tices - is not easy. The cur­rent rigid and over­sized in­fra­struc­ture plat­forms don't help here.

So it's time for some­thing dif­fer­ent: dis­cov­er our in­creas­ing­ly pop­u­lar "no-appserv­er-par­a­digm", en­abling you to use all of the en­ter­prise fea­tures with­out the heavy plat­form bur­den...

Down­load the full ar­ti­cle here!

Some peo­ple will claim that REST does not need BPM be­cause it pro­vides all the se­man­tics you need.

How­ev­er, if you look be­neath the hood then it turns out that this is not ex­act­ly true: in par­tic­u­lar, if mul­ti­ple (in­de­pen­dent) REST ser­vices need to come to the same out­come then you want some­thing more...

Won­der­ing what that is? Good! It's all ex­plained in one of our lat­est pub­li­ca­tions - to learn the de­tails: just fill out this form.

En­joy!