So microservices as they appear from Martin’s & James’s article is pretty much service orientation without some of the bad misconception that tied into the SOA moniker like WS*, ESBs as a must, etc., perhaps that’s a good enough reason for a new name but personally I doubt it.
In ActiveMQ messages can be prefetched to consumers. Let say a consumer gets 1000 messages prefetched but for some reason disconnects after consuming and acknowledging 900 messages. When the broker looses the connection to the consumer, it knows that out of the 1000 prefetched messages only 900 were acknowledged, so the remaining 100 messages will get the JMSRedelivered flag set to true to indicate that these messages get redelivered.
As some of you may know, ECF's implementation of OSGi Remote Services has support for asynchronous proxies. This allows consumers of remote services to easily use asynchronous/non-blocking invocation to access a remote service.
Well, you probably know my thoughts on cloud, PaaS, iPaaS and the like. In short, there’s a lot of hype around it, unscrupulous vendors, and some awesome magic involved. But there is some truth to it when you live in reality.
After two great APISTRAT events last year, the first European event in Amsterdam kicked things of this year – and duly delivered another great few days of content and discussions. The tweet stream says in all on how engaged people were: the keynotes and sessions just got better an better.