Today I am writing from Luxembourg, where I participated in the negotiation meetings of two EU projects that are being launched. I'll write about them when they will actually signed.
Not far from here, in Dagstuhl 2010, we worked on the "event processing manifesto" . Today I discovered another manifesto that I think can be tracked to EPFL in Laussanne (not completely sure since the manifesto authors don't identify themselves), the manifesto is called "The REACTIVE MANIFESTO" and is dated July 15, 2013. The picture above is copied from the manifesto, and as you can see they define REACTIVE as event-driven, scalable, resilient, and interactive. I wonder what is the background and motivation about it, perhaps one of this Blog readers will be able to shed light...
2 comments:
This manifesto actually looks like a reinvention of CORBA/Eventing/Notification Service or J2EE/JMS. It's the usual architecture of a distributed multitier system. Every application server or object monitor is highly or limitless scalable, highly or limitless available, fail-over, ... all these typical attributes why such platforms are invented in the Nineties as a precondition for Internet applications, these platforms even do much more. CEP is not mentioned ... There are no references or literature, no state-of-the-art in this manifesto.
Do you write an pro-active manifesto now?:-) On the first day of our 2nd CEP Dagstuhl seminar in May 2010 http://www.dagstuhl.de/Materials/Files/10/10201/10201.SWM14.Paper.pdf, the 50 participants decided not to write a manifesto at all - I remember all the arguments from Alex Buchmann, Mani Chandy, Jean Bacon, et al.
The motivation and scope seems to be "Reactive Programming". So the manifesto is programming language-centric (discussing futures, callbacks, ...).
Authors are Bruce Eckel, author of "Thinking in ..." books and Jonas Boner, creator of Akka and CTO of Typesafe.
See InfoQ: Reactive Programming as an Emerging Trend with some background and also a reference to Gartner inlcuding "Reactive Programming" in the Hype Cycle for Application Development, 2013.
Post a Comment