Facebook Thrift, now a member of the Apache Incubator is a cool way
to create cross-language Services.
What does cool mean? Its efficient, fast, and works with native apps,
(damn it). It is actually being used by Evernote, Imeem and
Facebook itself.
I find the Evernote Developers' API quite interesting (Check out this
PDF in particular). They seem to have a lot of native apps optimized
for specific devices that use the same thrift service for
synchronization funcitionality.
I wonder how this compares to the usual Java Application stack, normally
made out of
- Spring Web/MVC
- Service Layer exposed (via Enunciate) as ReST/SoAP or XML-RPC
- Spring ORM for persistence
Security via Spring Security/SSL-layer? Native clients connect via
XML-RPC/SSL ?
I was just wondering how nicely ReST and XML-RPC integrate into Spring.
Spring Remoting is for java<->java remoting AFAIK.
Maybe I will have some time to compare both approaches...