Integration intervention: Get your apps and data up to speed

22
1 RED HAT JBOSS MIDDLEWARE Beyond Big Data Webinar Series Integration intervention: Get your apps and data up to speed Syed Rasheed Solutions Marketing Manager Kenny Peeples Technology Evangelist November 19 th , 2014

Transcript of Integration intervention: Get your apps and data up to speed

1 RED HAT JBOSS MIDDLEWARE

Beyond Big Data Webinar Series

Integration intervention: Get your apps and data up to speed

Syed RasheedSolutions Marketing Manager

Kenny PeeplesTechnology Evangelist

November 19th, 2014

2 RED HAT JBOSS MIDDLEWARE

IT EVOLUTION LEAVES ORGANIZATIONS WITH MULTIPLE COMPUTING MODELS

3 RED HAT JBOSS MIDDLEWARE

PROBLEM 1: MONOLITHIC APPLICATIONSINFLEXIBLE, INEFFICIENT, HARD TO MAINTAIN

Print Invoices

Generate POs

Credit Verification 1

User Authentication 1

Account Validation 1

Create Customers

Credit Verification 2

User Authentication 2

Account Validation 2

• Application functionality and processes are not designed to manage data for use beyond its own boundaries

• Data is out-of-sync, incomplete, and inaccurate in your applications

• Hard to adapt to changing business requirements

• Duplication of functionality means wasted resources

• Small fixes require large investments of time and labor

4 RED HAT JBOSS MIDDLEWARE

PROBLEM 2: POINT-TO-POINT INTEGRATIONISN’T JUST A DATA PROBLEM… IT’S A PROCESS AND FUNCTION PROBLEM TOO

● Each project “re-invents” the data access layer:– Reduces developer productivity

– Increases maintenance costs

– Raises operating risks, system failures, downtime

BI ReportsAnalytical

ApplicationsSOA Services

Custom Applications

Mobile Applications

Hadoop NoSQL Cloud Apps Data Warehouse & Databases

Mainframe XML, CSV& Excel Files

Enterprise Apps

Integration Complexity

Constant Change

Siloed &Complex

Data Consumers

DataSources

5 RED HAT JBOSS MIDDLEWARE

BREAKING THE MONOLITHService Oriented Architecture???

Classic SOA

• Integration of different applications as set of services

Microservices

• Architecture for single application as set of services

Both are SOA but different implementation approach

6 RED HAT JBOSS MIDDLEWARE

BREAKING THE MONOLITH STEP 1

Services

OLTP System

Master Data ERP AppCloud App

Mainframe

SalesFinanceMarketing Human Resources

Point 2 Point Spaghetti

Analytical Applications

Custom Applications

Mobile Applications

Point 2 Point Spaghetti

7 RED HAT JBOSS MIDDLEWARE

BREAKING THE MONOLITH STEP 2

ESB for Service Virtualization & Abstraction

Services

OLTP System

Master Data ERP AppCloud App

Mainframe

SalesFinanceMarketing Human Resources

Integration Complexity

Analytical Applications

Custom Applications

Mobile Applications

Decouple the client from the service implementation

However business service implementations are often intertwined with data access and transformation code

8 RED HAT JBOSS MIDDLEWARE

BREAKING THE MONOLITH STEP 3

ESB - Service Virtualization & Abstraction

Services

OLTP System

Master Data ERP AppCloud App

Mainframe

SalesFinanceMarketing Human Resources

Analytical Applications

Custom Applications

Mobile Applications

Data Bus - Data Virtualization & Abstraction

Data bus allows for virtualization i.e. decoupling of the enterprise data access and reduce coupling between services.

Explicit separation of concerns between implementation of the service functionality (business logic) and enterprise data support logic.

9 RED HAT JBOSS MIDDLEWARE

DESIRED SOLUTION

Data as a Service

● Standard based interface

● Contextual view of disparate source data

● Single point of access / integration

● Reuse of Data

But you cannot achieve this by writing more application code…

Hadoop NoSQL Cloud Apps Data Warehouse & Databases

Mainframe XML, CSV& Excel Files

Enterprise Apps

Data SourcesSiloed & Complex

Data as a Service

BI ReportsAnalytical

Applications

Enterprise Integration /

SOA

Custom Applications

Mobile ApplicationsREST Request

SQL Statement SOAP MessageREST Message

JSON Results

10 RED HAT JBOSS MIDDLEWARE

Expose all data through a single uniform interface

Provide a single point of access to all business services in the system

Expose data using the same paradigm as business services - as "data services"

Expose legacy data sources as data services

Provide a uniform means of exposing/accessing metadata

Provide a searchable interface to data and metadata

Expose data relationships and semantics

Provide uniform access controls to information

DATA AS A SERVICE / DATA BUS SOLUTION

11 RED HAT JBOSS MIDDLEWARE

SUPPORT FOR ODATA Standard Data Access Protocol for Web i.e. “ODBC for Web”

● OData is a standardized protocol for creating and consuming data APIs. Builds on core protocols like HTTP and commonly accepted methodologies like REST. The result is a uniform way to expose full-featured data APIs.

● Widely adopted by SAP, Salesforce.com, Microsoft, IBM and RedHat along with Netflix, Open Data Government Initiative, Facebook Insight etc.

● JBoss Data Virtualization is both OData producer & consumer i.e.

– JDV expose Virtual Database using the OData protocol and

– Easily consume data exposed using the OData protocol.

Making it extremely easy for both developers and business users to utilize data in standardize way.

Example:

SQL Query Odata Request

Select * from products where name = ‘Milk’ …/products?$filter=name eq ‘Milk’

12 RED HAT JBOSS MIDDLEWARE

JBOSS FUSE + DATA VIRTUALIZATION BETTER TOGETHER

&DEMONSTRATION

13 RED HAT JBOSS MIDDLEWARE

JBOSS DATA VIRTUALIZATION – DATA BUS

14 RED HAT JBOSS MIDDLEWARE

JBOSS FUSE – ENTERPRISE SERVICE BUS

Benefits of Fuse with Data Virtualization • Multiple components and flexibility

with Camel• Integration with Camel on multiple

platforms

15 RED HAT JBOSS MIDDLEWARE

MICRO DATA SERVICES WITH DATA VIRTUALIZATION

• Exposing Aggregated Data services to an integration platform• Become more productive• Use abstraction with Data Services and stop monolithic applications• Build Components into services

http://martinfowler.com/articles/microservices.html

16 RED HAT JBOSS MIDDLEWARE

WORKING WITH DATABASES WITH CAMEL

● JDBC component - Allows you to access JDBC APIs from a Camel route. Producer Only

● SQL component - Allows you to write SQL statements directly into the URI of the component for utilizing simple queries. Consumer and Producer.

● JPA component - Persists Java objects to a relational database using the Java Persistence Architecture.

● Hibernate component - Persists Java objects using the Hibernate framework. Camel-extras project on Google.

● MyBatis component - Allows you to map Java objects to relational databases.

● Olingo2 Component - interact with OData 2.0 and 3.0 compliant services

17 RED HAT JBOSS MIDDLEWARE

APACHE CAMEL OLINGO2

● Available as of Camel 2.14

● The Olingo2 component utilizes Apache Olingo version 2.0 APIs to interact with OData 2.0 and 3.0 compliant services

● URI Format – olingo2://endpoint/<resource-path>?[options]

● Will be part of JBoss Fuse 6.2

● Easy integration with Data Virtualization

18 RED HAT JBOSS MIDDLEWARE

ODATA BASICS

● An OData client accesses data provided by an OData service using standard HTTP. The OData protocol largely follows the conventions defined by REST, which define how HTTP verbs are used. The most important of these verbs are:

– GET: Reads data from one or more entities.

– PUT: Updates an existing entity, replacing all of its properties.

– MERGE: Updates an existing entity, but replaces only specified properties.

– POST: Creates a new entity.

– DELETE: Removes an entity.

● OData provides full metadata of the datasource. With a $metadata query it is possible to see the full structure of the data available from a given OData service, as well as data types, relationships, etc.

http://www.odata.org/

19 RED HAT JBOSS MIDDLEWARE

DEMO SCENARIO

Data Virtualization Server

Postgres

Application

MySQL

OData

• Data abstraction for DB modernization and migration

• Minimize impact by creating “logical” data views of underlying sources

• Expose logical model as SQL or data services

20 RED HAT JBOSS MIDDLEWARE

INSERT SCREEN

SHARE HERE

21 RED HAT JBOSS MIDDLEWARE

SUMMARY & CALL TO ACTION

● Access, refine, distribute & monetize all your data with agility & efficiency

● Use modular architecture & start refactoring your monoliths and data silos

● Red Hat JBoss middleware platform can support your choice of architectural style

Monolith SOA Microservices

22 RED HAT JBOSS MIDDLEWARE

Wednesday, November 5, 2014 The 3 big problems with data and how to avoid themSyed Rasheed, senior product marketing manager, Red HatKen Johnson, director of product management, Red Hat

Wednesday, November 12, 2014 Slow data is a fast way to lose your best customersVamsi Chemitiganti, chief solution architect, Red Hat

Wednesday, November 19, 2014Integration intervention: get your apps and data up to speedSyed Rasheed, senior product marketing manager, Red HatKenny Peeples, JBoss technology evangelist, Red Hat

Tuesday, December 2, 2014 Making good decisions? Want to? Data analytics is the key.Kim Palko, senior product manager, Red HatPrakash Aradhya, senior product manager, Red HatKenny Peeples, JBoss technology evangelist, Red Hat

Tuesday, December 9, 2014 Don't let Hadoop become a new data siloSyed Rasheed, senior product marketing manager, Red HatKenny Peeples, JBoss technology evangelist, Red Hat

To watch the entire series – live or on

demand - register at:

http://bit.ly/1wzD5Lx