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:

130852: UniqueIdM­gr: java.lang.Run­timeEx­cep­tion: Al­ready writ­ing a new ver­sion

Fixed cleanup of re­sources when writ­ing a new epoch file, to avoid ex­cep­tions un­der ab­nor­mal op­er­at­ing con­di­tions.

A few weeks back we've been send­ing around this poll via our newslet­ter sub­scriber base. We got a lot of an­swers so I will not go into every sin­gle one of them (and we can't send in­di­vid­ual replies, BTW, be­cause the sur­vey was anony­mous). How­ev­er, here is a dis­til­la­tion of the re­sults, and our com­ments / ques­tions to each.

127485: READONLY does not call Syn­chro­niza­tion - lead­ing to con­nec­tion leak with JDBC/JPA/XA Trans­ac­tions

If two or more data­bas­es are in­volved, and all DBMS trans­ac­tions are read­on­ly, then the con­nec­tions are not re­turned to the pool be­cause Syn­chro­niza­tion call­backs are not done prop­er­ly. This has been fixed.

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...