Upload
chanaka-fernando
View
68
Download
0
Embed Size (px)
Citation preview
ESB 4.9.0 Release Webinar
● Chanaka Fernando
● Prabath Ariyarathna
Agendao Modern enterprise and ESBo WSO2 ESB featureso What is new in WSO2 ESB 4.9.0?
- Inbound Endpoints - Coordination support for scheduled tasks - MSMP improvements - Extended support for MQ protocols (Kafka, MQTT, RabbitMQ)o Connector storeo Performance and Stability
Modern Enterprise and ESBo Modern Enterprises - Comprised of so many heterogenous systems
and services- built based on open standards, custom-built,
acquired from a third party, part of a legacy system or any such combinationo Integration- Organizations move away from monolithic systems- Multiple Systems connected via SOA as the blueprint
Modern enterprise and ESBo Spaghetti integration
Hard to -maintain -scale -troubleshoot -govern
Modern enterprise and ESBo ESB – The standard infrastructure to
implement the SOA Easy to -maintain -scale -troubleshoot -govern
WSO2 ESB overview
o A lightweight, high performance ESBo Comprehensive REST, SOAP, WS-* support o 100+ Connectors (Salesforce, Paypal, Twilio and many more) o SAP, FIX, HL7 - Domain specific solutionso Zero Code/Configuration driven o Extensible and Scalable
New features (Inbound Endpoints)
o Creating inbound messaging channels dynamically. o Listening Inbound – HTTP, HL7, TCP, WS-RMo Polling Inbound – JMS, File/VFS
o Injects messages directly from transport layer to mediation layer without going through the axis engine
o Supports multi-tenancyo Dedicated thread pools per inboundo Built-in cluster coordinationo Extending the functionality with custom inbound endpoints
Listening Inbound Endpoints
o Starts message listening interfaces dynamically o Eg: HTTP Inbound – Dynamically create HTTP inbound message interfaces on a specified port
and inject the messages into ESB message flow o Fully supported in multi-tenant environments.o HTTP, HL7, WS-RM, TCP Inbound Endpoints o Message filtering capabilities with HTTP inbound
Polling Inbound Endpoint
o Dynamically creates message polling interfaces. o Eg: JMS Inbound Endpoint – polls a given JMS queue and inject messages into an ESB
message flow. o Fully supported in multi-tenant environments o Coordination support o JMS, VFS/File Inbound Endpoints
Polling Inbound Endpoint - Coordinations
o One consumer per cluster vs multiple consumers
Single Consumer Multiple Consumers
New Feature (Scheduled Tasks - Coordinations)o Executing tasks in a clustered or multi-tenant environments.o With the cluster coordination support, tasks will always run on an available
node in contrast to the pinned server concept which was used with earlier versions
o Two modes of operation- Run in a single node (one task per iteration)- Run in multiple nodes (n tasks per iteration)
Scheduled Tasks - Coordinations
o Executing tasks in a clustered or multi-tenant environments.o Leader election/failover support
Enterprise Messaging
o Kafka, MQTT and RabbitMQ support
Enterprise Messaging (Kafka support)
o Apache Kafka is publish-subscribe messaging rethought as a distributed commit log.
o Fast, Scalable, Durable and Distributed by designo Kafka inbound endpoint to connect to inbound connectionso Kafka connector for outbound communicationo Two modes of operation
- High level- Low level
Enterprise Messaging (MQTT support)
o Lightweight broker-based publish/subscribe messaging protocol o Designed to be open, simple, lightweight and easy to implement. o Ideal for use in constrained environments like mobile devices and IOT.o Improved MQTT transport(axis2 transport) listener-sender implementation.o MQTT inbound endpoint for more versatile integrations
Enterprise Messaging (RabbitMQ support)
o Robust, easy to use, well supported messaging solutiono Improved the stability of the rabbitmq transport (axis2 transport)o Automatic connection recovery for RabbitMQ transport in case of failureo All content-types are now supported by RabbitMQ transporto Introduced the new feature rich inbound endpoint for rabbitmq o Added the SSL support for rabbitmq inbound/transport
Message Store Capability Improvements
o JDBC Message Store.o Easy to connect.o Quick transactions.o Ability to work with a high capacity for long period of time.
o RabbitMQ Message Store.o Robust messaging for applications.o Easy to use
Message Processor - Coordinations
o Fully supported in multitenant environmentso One consumer per cluster – Guaranteed in-order deliveryo Multiple consumers – Guaranteed delivery
Single Consumer Multiple Consumers
Failover Message Store Message Processor
o Failover Store.o This allows the message store to store messages in the failover message store if the original
message store is not available.o Scheduled Failover Message Processor.
o Move messages which were forwarded to the failover message store to the original message store when it becomes available again.
140 + Connectors
o A connector is a ready made and convenient tool to reach web API’s.o ESB Connector Store(www.store.wso2.com) : 140+ connectors.
Performance and Stability
o Fastest open source ESB.o Battle tested for most extreme
conditions across numerous deployments.
o Proven case studies – handling billions of transactions.
o Performance improvement over the ESB 4.8.1
Q & A