An open web of employees, partners, suppliers, and customers drives business activities. The activities rely on reliable and timely B2B/B2C/B2E interactions; provided by APIs interconnecting business processes and data. Although, architects and developers implementing APIs prefer to follow REST principles and use lighter-weight integration technologies (e.g. JSON, HTTP, and POX), they often struggle to expose RESTful APIs due to technical infrastructure limitations. This workshop will focus on how to expose your heterogeneous back-end data entities, processes, and services as a RESTful API in a quick, simple, easy, and architecturally sound manner, using the WSO2 Platform.

Presented by:

Hiranya Jayathilaka, Product Lead, ESB

Hiranya, WSO2 Enterprise Service Bus product lead, is an expert in HTTP and spearheads the work on supporting REST APIs within WSO2 ESB and the WSO2 Carbon enterprise middleware platform. Hiranya is a long-time committer on the Apache Synapse and Apache Xerces2/J projects; author of the FIX transport for Apache Synapse; and a contributor to several other open source projects, including Apache Derby and Apache Web Services. He is also a pioneering member of the project MOINC, which is focused at leveraging grid computing and volunteer computing principles to implement highly scalable Web services clusters.

Chris Haddad, VP Technology Evangelism

As Vice President Technology Evangelism Chris raises visibility, awareness, and knowledge of the Carbon and Stratos platforms. He works closely with developers, architects, or C-level executives to increase WSO2 technology adoption, improve the middleware platform, and maximize customer value. Prior to joining WSO2 Chris led research teams at Burton Group and Gartner advising Fortune 500 enterprise organizations and technology infrastructure vendors on adoption strategies, architecture, product selection, governance, and organizational alignment. His team advanced best practices in Platform as a Service, Cloud Application Architecture Patterns, Service Oriented Architecture, and application middleware.

Topics to be covered:

• API Architecture

  This session describes standard business requirements and how to design a simple, consumable RESTful API. The approach will follow REST methods, principles, and best practices to design and develop the service while leveraging the existing IT infrastructure. The session will address how to enhance the API using RESTful techniques (i.e. HATEOS, MIME types) and describe API design best practices.

• Writing REST services

  This session describes how to code RESTful APIs exposed with a REST binding by using the Java REST API, JAX-RS. The demonstration will illustrate how WSO2 Application Server hosts JAX-RS services.

• Mediating legacy services and securing the RESTful API using the API Gateway pattern and WSO2 ESB

  This session will describe how to configure the WSO2 ESB to follow the API gateway pattern and expose back-end entities, processes, and services as a RESTful API. The WSO2 ESB may be used to both publish using an HTTP endpoint and secure the API using REST-friendly security protocols (e.g. HTTP basic authentication or OAuth). This session introduces the latest first-level API configuration capability, which was recently added to WSO2 ESB.

• Providing RESTful Data Access

  Data entities and REST resources have a strong relationship. API architects commonly expose entities as a resource and provide CRUD operations using REST methods. WSO2 Data Services Server provides necessary out-of-the-box functionality to rapidly create REST resources from data entities.

• Beyond the APIs: API Store and Your Business as an API

  How can architects encourage API adoption within an enterprise environment? 
This session will discuss how enterprise API patterns can encourage API consumption and re-use. An API Store process pattern enables potential consumers to discover APIs, match business requirements, subscribe to APIs, and gain access credentials. The Your Business as an API pattern delivers Cloud-based API hosting infrastructure, which augments the API by enabling multi-tenancy, self-service configuration, billing and metering, and control. Overall, this pattern covers how vertical PaaS takes business APIs into the enterprise and out to partners, suppliers, and customers.

This workshop is aimed at technical and business architects who design APIs and developers who build APIs for different business domains.