I've presented my views before on what I see as the three megatrends in IT:
- Web 2.0 - or more generally, RIA
- Grid - although today I'd probably update this to be "Cloud Computing"
But the distinction between RIA and SOA has always felt forced; unrelated working metaphors, owing more to the historical segregation of the communities addressing each than strict architectural principles.
While industry lines have been drawn very clearly around these two domains (take OpenSOA v. OpenAJAX for example), there have been many attempts to nibble away at the distinction. AJAX toolkits like SAJAX and SWATO strive to make calling back-end resources more convenient. And frameworks like ADF approach the problem from the other end, by "hiding" AJAX rendering in their server-side, SOA-aware paradigm.
So what has Appcelerator got to do with this?
From what I understand so far, the key is that they have unified the event/messaging model both within the browser and the "SOA-sphere", and done so in a very elegant way. There are three parts to their solution:
- Web Expression Language
- RIA Widget Framework
- RIA Message Broker
All components in an Appcelerator application communicate via simple lightweight messages using the RIA Message Broker. On the server-side, Appcelerator provides a set of SOA Integration Points that enable service creation in Java, PHP, Ruby, .NET, Python and Perl.
The end result is a very clean, lightweight and seemless development approach. HTML attributes define behaviour: what messages to send, and what to do when a message is received. And the real magic: when you send a message, you do not know or care if it handled by another HTML element on the same page, or a SOAP Web Service somewhere out on the net.
Here's how straight-forward it gets. An example of an input button messaging a calendar widget to show itself..
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:app="http://www.appcelerator.org">
<app:calendar title="Pick a Date" on="l:show.calendar then execute" inputId="mydate">
<input type="text" id="mydate" value="click me" on="focus then l:show.calendar"/>
Or an input button sending a message...
<input type="button" value="submit" on="click then r:login.request"/>
.. that is handled by a Java service:
public class LoginService
@Service(request = "login.request", response = "login.response")
protected void processLogin (Message request, Message response)
// get request data
String username = request.getData().getString("username");
String password = request.getData().getString("password");
User user = userDAO.login(username,password);
// format response
if (user != null)
Appcelerator looks like one to definitely watch closely and investigate further..