Architecture and SOA

The Architecture and SOA track focuses on the structure behind applications, examining different approaches to designing applications that perform and scale, including SOA, REST, JMS, and OSGi. This gives you the ability to examine the application infrastructure, technical requirements, and available tools and make the right decisions on architecture and design for building higher quality and more useful applications. The Architecture track then takes Service-Oriented Architecture and dives deeply into how it can best be implemented under a variety of different technical requirements, including SOA design strategies, use of enterprises service buses (ESBs), and emerging applications of SOA for complex problems such as event processing.

Architecture and SOA sessions already confirmed:

• Creating an Event-Driven SOA
• Practical Web Service Design and Development
• Resource-Oriented Enterprise Service Bus

---

Creating an Event-Driven SOA

Eben Hewitt, Author, Java SOA Cookbook

Building an Event Driven Architecture (EDA) can be much easier when built on a SOA foundation. But each of these architectural strategies has their own constraints and tools. A Complex Event Processing engine can aid in risk management, fraud detection, monitoring, reporting, as well as business and operational intelligence. But you need a service-oriented infrastructure implemented with a set of patterns that go beyond integration and process engines to truly realize EDA.This session shows you how to create an Event-Driven SOA so you can build systems that maximize loose coupling and provide rich data analysis opportunities in near time.

Eben Hewitt is the author of five technical books, including O’Reilly’s Java SOA Cookbook, and a contributor to 97 Things Every Software Architect Should Know. In this session he demonstrates what EDA is, the tools and patterns that comprise it, how it can work with SOA, the differences between Complex Event Processing and Event Stream Processing, how to define service interfaces that are ready for EDA, and how to integrate key platform tools such as an ESB, brokers, and Event Processing engines in order to begin practical work using events. He also examines an array of popular Event Processing engines so you can make an informed decision for your projects.

After attending, you’ll be able to:

• Understand what EDA is and how it can complement and extend the power of SOA;
• Identify open source EDA tools and compare the advantages and disadvantages in their performance, ease of use, and querying languages;
• Implement services and brokers in a way that specifically takes advantage of the benefits offered by an event-driven approach;
• Use the Esper Event engine for CEP and ESP on top of a SOA platform to create Event Driven Services and Processes that handle real-world problems.

---

Practical Web Service Design and Development

Ryan Heaton, Lead Developer, Enunciate, OAuth and OFX4J

This session is a discussion about the architecture and design of a Web service API. Understand the complexities of designing a functional Web service API and understand the right questions to ask when evaluating your own architecture for providing Web services, taking into account your own requirements and specifications.

For example, when do we use REST and what are the principles to conforming to a RESTful architecture? When would we use SOAP and what advantages and disadvantages does SOAP have over REST? What serialization formats are available? When and how would we apply XML, JSON, AMF, etc. to our API? What do the Web service APIs of the industry big-players (e.g. Google, Facebook, Twitter, Flickr, Netflix...) look like? How do we secure our Web services? How can we leverage Web services to provide a rich development platform for our data ala Facebook, Twitter, Google and Netflix? What's the best way to leverage certain technologies such as ATOM, GData, and RDF?

The nature of Web service APIs has made a recent and significant shift to accommodate a new and broad set of use cases. While still providing for traditional server-to-server and Internet-aware desktop applications, Web services have enabled applications to move to the cloud and are providing a rich set of services and functionality for mobile devices and rich web applications. Never has it been more important to understand how to correctly design a Web service API that meets the practical needs and requirements of the use case.

In this session you gain:

• A better understanding of the current and ever-changing landscape of Web service development;
• Familiarity with the proven principles and techniques for effective Web service API design;
• A glimpse of what other successful industry players are doing and how a good Web service API promotes their agenda;
• And more.

---

Resource-Oriented Enterprise Service Bus

Jeremy Deane, Technical Architect, Collaborative Consulting

Are you looking for an alternative to expensive complex enterprise integration solutions; one that will translate into better service management and scalability? Jeremy Deane, an expert in Resource-Oriented Architecture, Performance Engineering and Software Process Improvement, discusses the convergence of Resource-Oriented Architecture and Enterprise Integration Patterns.

An Enterprise Service Bus (ESB) provides a platform for service provisioning. The core capabilities that enable provisioning across an enterprise include addressing, routing and transformations. Addressing is the ability to specify the location of a service regardless of transport. Service routing defines a message path across a number of servers or nodes and message content transformations are implemented using XML technologies such as XSLT and proprietary adapters. Resource-Oriented Architecture goes beyond RESTful web services to provide a more extensible and transport independent foundation. A Resource-Oriented approach not only decreases time to market and lowers the cost of entry but pushes the integration functionality to the edge of the network (as a URI), translating into better service management and scalability.

This session reviews:

• The key concepts of an Enterprise Service Bus (ESB) and Resource-Oriented Architecture;
• The key concepts of a Resource-Oriented ESB;
• Several service examples using 1060 Research’s NetKernel;
• And more.