Son of SOA: Resource Oriented Computing and Event Driven Architectures
d2573703-b8f3-42d6-a5c2-2ba6c9ae3321
|
Presentation |
Resource Oriented Computing systems process resource representations, execute transformations and computations by defining processing in terms of compositions and asynchronous sequences of resource requests. Application development and deployment using SOA faces problems when organizational changes occur if the participating systems (service providers and consumers) are too tightly coupled. In SOA, messages and systems are inherently synchronous, promoting dependencies that filter to the organizational level. Resource Oriented Computing solves system and application integration issues by leveraging ESB, domain-specific languages, and shared memory mechanisms for integrating coupling points, not the applications themselves, by promoting event-driven interactions between system components, and by creating logical mappings of resources such as data or computations that are abstracted from the physical manifestation of the system deployment.
Who should attend
- Infrastructure architects
- Application architects
- Senior developers
- Application development managers
Why do attendees need to be aware of this information today?
- Systems are built through the integration of decoupling points via ESBs, domain-specific languages, and shared memory mechanisms instead of direct integration of services, which is less flexible and more expensive in response to workflow or organizational changes
- Event-driven systems allow for shorter time-to-market application development and integration independently of organizational changes
- Treat computational resources as addressable entities (i.e. via object references, URIs, callbacks, etc.) that may be consumed on-demand rather than being intrinsically tied to specific applications
- Event-driven systems can be implemented by leveraging existing infrastructure and SOA investment
- Balance open-source vs. commercial products to avoid lock-in that results in higher costs and little or no flexibility during integration
What basics should attendees know before attending this session?
- Enterprise service bus
- Basic understanding of distributed data caching technologies
- Enterprise integration patterns and SOA
- Event-driven distributed programming basics
- Java 5 or later
- Domain-specific language basics
What problem(s)/challenge(s) will an attendee learn to solve by attending this session?
- How to develop complex applications within very tight deadlines by formalizing system integration around a resource-oriented model
- How to turn SOA-based systems into callbacks, breaking the rigid provider/consumer model
- How to develop event-driven applications based on technologies and services already in production using a multi-language approach
- How to integrate the existing applications by applying event-driven rather than centralized control techniques
- How to extend SOA beyond transactions to include workflow processes and lossless transformations of resources from one representation to another
What else will attendees learn by attending this session?
- Real world applications that use Mule ESB, OpenSpaces, Terracotta and OSGi
- Examples of architecture, service objects, configuration files
- Approaches to solving distributed data caching
-
Eugene CiuranaEugene is the Director of Systems Infrastructure at LeapFrog Enterprises, the largest educational toy company in the United States, and he is also a contributing editor to TheServerSide.com. In 2006 he led the first-time adoption of Linux and other open-source technologies at Wal-Mart Stores Information Systems Division as chief liaison between Walmart.com Global and the ISD Technology Council.



Intermediate
Enterprise application development and integration