This will be Richard Hightower's first public speaking engagement in 2 years.
Talk Title: Project X - iSO2 - in-memory service oriented objects. (Websocket and SOA 2.0+) to support next-gen SOA and back-end for mobile and SPAs.
Join us on Wednesday, August 28, 2013 from 6:00 PM to 7:00 PM (PDT)
Palo Alto, CA
3101 Park Blvd.
Palo Alto, CA 94306
To register click here: http://www.eventbrite.com/event/7988629205/es2
ProjectX is a next generation in-memory SOA system. ProjectX exposes Resin internal tech (disruptor-ish based on principles of mechanical sympathy), geared towards non-blocking nature to take advantage of multi-core machines, to developers at large. ProjectX creates a services system that allows developers to create high-speed, in-memory services that can manage operational data (data safety) through replicated journals, which allows SOA architectures to avoid unnecessary mapping to databases, database bottlenecks, and cache coherency issues by re-inverting the inversion of control of data back from the database to live near the code that implements the business logic (you know OOP).
ProjectX addresses the communication backbone needs of next generation HTML 5/SPAs, and rich interactive mobile applications, as well as allowing developers to quickly develop scalable services (SOA). ProjectX services are exposed via JSON or Hessian over HTTP or WebSocket to support SOA services and SPA/Mobile backbones. And unlike plain REST and SOAP services, ProjectX services are designed to be bi-directional so services can invoke methods on clients and publish events to clients. ProjectX has a guaranteed message channel, a clustered message channel, a WebSocket channel and a HTTP channel. ProjectX publishes two easy to implement wire protocols HAMP and JAMP (JSON based) so other languages can invoke and be invoked by ProjectX services. ProjectX provides a services module system which allows teams to work on related services with independent release cycles (you can inject services written in different war files and there is a mechanism of versioning that allows a war module to support multiple versions of services as well as deploying different war files that implement different versions of the service).
If you want to read more:
Who is Richard (Rick) Hightower?
If you can't go, read this:
"...new and better way to quickly build fast, scalable services that are exposed through not only REST but also through Websocket services. They also seem to be coining a new term (In-Memory) "Object Oriented Services" in this series. And just to be clear, when I say 'intense' I mean that this review goes as far down as the hardware level."