Вы находитесь на странице: 1из 21

ESB to Event-

Driven iPaaS
The Architect’s Guide to Building
a Modern Data Integration Platform

By 2020, event-sourced, real-time situational
awareness will be a required characteristic
for 70% of digital business solutions, and
80% of new business ecosystems will require
support for event processing.”


-SOURCE: GARTNER “TOP 10 STRATEGIC TECHNOLOGY TRENDS FOR 2018: EVENT-DRIVEN MODEL.” 8
MARCH 2018, YEFIM NATIS, DAVID CEARLEY, MIKE WALKER, BRIAN BURKE.

In iPaaS we find the groundwork being


laid for a digital future, as the products
in this segment are lighter, more agile IT
infrastructure suited for the rapidly evolving
use cases around digital business.”
-SOURCE: “GARTNER SAYS WORLDWIDE APPLICATION INFRASTRUCTURE AND MIDDLEWARE MARKET GREW
12 PERCENT IN 2017.” 4 JUNE 2018. HTTPS://WWW.GARTNER.COM/NEWSROOM/ID/3877263

Text copyright © Solace

All rights reserved. No part of this work may be reproduced, or stored in a retrieval system, or transmitted in any form
or by any means, electronic, mechanical, photocopying, recording, or otherwise without permission from Solace.

For inquiries about permissions, contact:

Solace
535 Legget Drive, 3rd Floor
Ottawa, Ontario K2K 3B8
Canada

Phone: +1 613-271-1010
Web: solace.com
TABLE OF CONTENTS
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Integration and the Introduction of an ESB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

8 Integration Challenges Architects Must Overcome to Achieve Digital


Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Baking agility into your infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Integrating IoT device and data into your enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Giving legacy systems access to cutting-edge cloud services . . . . . . . . . . . . . . . . . . . . . . 5

Linking globally distributed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Ensuring application portability across hybrid and multi-cloud . . . . . . . . . . . . . . . . . . . . 6

Guaranteeing delivery (embracing “eventual consistency”) . . . . . . . . . . . . . . . . . . . . . . . 6

Avoiding API and protocol lock-in through open standards   . . . . . . . . . . . . . . . . . . . . . . 7

Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

How event-enabled iPaaS unlocks true digital transformation. . . . . . . . . . . . . . 8

Common iPaaS design patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Enter the advanced event broker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

How to event-enable your iPaaS with an advanced event broker . . . . . . . . . . 11

Decouple systems through subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Bridge synchronous and asynchronous interactions. . . . . . . . . . . . . . . . . . . . . 12

Case Study: Consumer Packaged Goods Company . . . . . . . . . . . . . . . . . . . . . . 13

Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

About Solace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 Upgrading Your ESB to Event-Driven iPaaS


INTRODUCTION
Additionally, today’s empowered consumers
expect real-time responsiveness, and
business leaders are tasked with being able
to do so with finer levels of granularity than
ever before.

Companies around the world and in every Simply put, current architectures and

sector are striving for digital transformation— infrastructures are not able to keep up.

the incorporation of AI, hybrid cloud, mobile One key to success is evolving your
computing and IoT into their business architecture and business processes from
practices. Such transformation promises request/reply to event-driven. As analysts at
to improve situational awareness and Gartner put it, “By 2020, event-sourced, real-
operational agility, and to help companies time situational awareness will be a required
build close, customized relationships with characteristic for 70% of digital business
their customers. solutions....(1)”

But these benefits don’t come easy. The other key: consuming integration as a

For most enterprises, pursuing those critical service (also known as Integration Platform as

benefits drives an astronomical increase a Service, or iPaaS) so it can adapt and scale

both in the number of systems and devices to support whatever comes your way.

they need to integrate and in the amount of This paper describes how you can upgrade
information flowing between those systems from your on-prem-centric enterprise service
and devices. bus (ESB) to an event-driven iPaaS approach
that will facilitate and in many ways future-
proof your digital transformation.

DID YOU KNOW ?

The iPaaS segment grew 60% in

2016 and 72% in 2017, making it

one of the fastest-growing software

segments.
Source: Gartner Newsroom (2)
INTEGRATION AND THE INTRODUCTION
OF AN ESB

Integration can be described as sharing state records and App B uses “CA.”
data between two otherwise separate This introduces the need to transform
systems, a process that consists of three that data at some point. You could
steps: transform California to CA as the data
moves directly from App A to App B, but
1. Data retrieval: read the customer
in systems with many producers and
record from App A;
consumers of information it makes sense
2. Data movement: move the customer to rationalize messages into a canonical
record from App A to App B, or normalized data format.
transforming payloads as necessary;
• Direct transformation: App A -> App B
and,
• Canonical transformation: App A ->
3. Data insertion: write the customer
Canonical -> App B, App C and App D
record into App B.
Canonical data formats allow for reuse
In the real world this becomes more
of data transformation mappings. They
complicated as App A usually represents
also add complications that are beyond
a record (a customer, for example)
our scope here, but suffice it to say
differently than App B.
complexity can grow to incorporate
Or let’s say App A uses “California” for not only complexities in the data
representation, such as nested data Infrastructure as a service (IaaS)
structures, but also in the relationships platforms provide hardware resources
between records. such as compute, disk, and network on
demand. And platform as a service (PaaS)
Think of a Return Material Authorization
added to that software platforms such
(when you want to return a product to a
as OS’s, databases, middleware, Java
store). There will be a customer record,
runtimes, and more.
maybe a warranty record, and a time of
purchase from the sales record—to name Then, with software as a service (SaaS),
just a few. complete applications were offered in
the cloud—first and still best exemplified
The complex relationships between those
by Salesforce.com. This evolution meant
records of information, both at rest and
that integration now had to extend
in motion, led to the advent of Enterprise
beyond the traditional LAN to include
Application Integration (EAI) software and
these cloud-based services and take
then enterprise service buses.
advantage of the benefits of cloud-native
ESBs retrieve data from source systems, deployment.
transform it as required, route it,
IPaaS addresses this need and brings
choreograph it, and write subsequent
traditional ESB capabilities to the cloud.
data into destination systems. This was
usually done over fast, reliable LAN
links within the walls of the enterprise
(corporate datacenters).

Eventually, the messaging layer was


abstracted from the transformation/
integration layer of the ESB because
reliable data transport scaled differently
and had its own set of requirements. The
key capability for data transport was to
guarantee that the data was delivered
securely, timely, and reliably.

With the growth of cloud-based services,


we’ve seen many critical capabilities shift
to the cloud.

3 Upgrading Your ESB to Event-Driven iPaaS


8 INTEGRATION CHALLENGES ARCHITECTS
MUST OVERCOME TO ACHIEVE DIGITAL
TRANSFORMATION

For companies with fairly simple, low- Things, events are what drive exchanges
volume, non-real-time integration of information. This means architects and
requirements, a simple integration developers need to shift their mindset
model might work fine: hub and spoke from being data-centric to event-centric.
architecture, request/reply interactions
Event-driven architectures enable greater
using RESTful HTTP.
agility, scalability and communication
But many companies—especially those across diverse cloud and datacenter
linking large numbers of applications and environments.
connected devices, serving multiple lines of
Here are some of the architectural and
business, or that have complex IT systems
operational challenges you will need to
that are distributed across datacenters
overcome to evolve toward an event-
and geographies—will need a more
driven architecture and ultimately achieve
sophisticated system.
success in your digital transformation
User expectations and information initiative if your system is complex, large or
technology are evolving from database- performance-sensitive.
centric request-based interactions to
event-centric, real-time interactions. From
social media platforms to the Internet of
BAKING AGILITY INTO YOUR across massive amounts of concurrent
INFRASTRUCTURE
connections.
The evolution of software development
Second, IoT devices exhibit different
practices and runtime environments means
characteristics and behavior than
applications can be created at a breakneck
applications, such as not being on or
pace. No app is an island, though, so if
connected all the time, and requiring very
you want to seize the advantages of rapid
low power/bandwidth communications
development and deployment you can’t
(many of which dictate the use of
forget rapid integration.
specialized APIs and communications
To do this, it’s critical to develop an event- protocols such as MQTT, which you need to
oriented data sharing infrastructure bridge with legacy APIs and protocols).
that makes it easy for apps to exchange
Command and control, especially at scale,
information with other systems so they can
is particularly difficult because you need to
play their part in business processes and
make sure that when a user clicks ”Unlock
transactions. Functionality is implemented
the door” that their car and only their car
as microservices, which consume and
reacts.
produce events.

This means microservices can be injected GIVING LEGACY SYSTEMS ACCESS TO


3 CUTTING-EDGE CLOUD SERVICES
anywhere into a choreographed flow as all
they care about is which event they need to The investment that enterprises have made
handle and whether they need to handle it in existing infrastructure is significant and
synchronously or asynchronously. can’t be thrown away. Many refer to their
way of dealing with this as “cap and grow,”
INTEGRATING IOT DEVICE AND DATA
2 INTO YOUR ENTERPRISE
meaning they cap their investment in
existing assets and link them to new assets
There are two reasons it’s hard to and infrastructure so they can gracefully
incorporate IoT into your business grow their infrastructure to meet new and
processes and decision-support systems. future needs.

First, IoT devices come in larger numbers This means they need to make new cloud-
than applications—tens of millions in native services, such as AI and machine
many cases. This demands sophisticated learning, accessible to legacy on-premises
aggregation, routing, filtration and fan-out systems across their enterprise.

5 Upgrading Your ESB to Event-Driven iPaaS


Legacy systems, such as mainframes or Doing so means both eliminating reliance
systems of record, are usually written on proprietary cloud-native services so that
in Java or C/C++ and will be around for you aren’t locked into any one cloud and
a long time; they will usually run on- embracing open standards so you aren’t
premises. IPaaS solutions must be able to locked into any one messaging technology
incorporate hybrid cloud capabilities that or event broker.
allow for events to flow to and from these
You can bet your business on one cloud,
older systems, as they occur, to the newer
you can run different applications in
systems that are built in the cloud.
whatever cloud best meets your unique
needs, or you can run multiple instances
4 LINKING GLOBALLY DISTRIBUTED
SYSTEMS
of the same applications in multiple clouds
for business continuity purposes. In any
Integrating applications and devices case, you need to build and integrate
running in diverse environments entails your applications in such a way that you
dealing with the realities of distributed can dynamically move workloads across
systems. Wide area networks (WANs) diverse on-prem and cloud environments.
are less reliable than LANs, and have
Today’s architects focus on building new
less bandwidth available and higher, less
architectures that let them leverage
predictable latency.
existing assets without being tied to
Given the increasingly distributed nature specific environments or technologies
of IT systems, you need WAN-optimized, moving forward.
encrypted, and lossless bridges between
different instances of your applications and
GUARANTEEING DELIVERY (EMBRACING
integration infrastructure so that events 6 “EVENTUAL CONSISTENCY”)
can flow across a global event mesh in a
guaranteed manner that optimizes WAN If you look at any data flow, you’ll
bandwidth. realize that not all nodes of the flow
must be synchronous. In fact, a very
small proportion of most flows must
5 ENSURING APPLICATION PORTABILITY
ACROSS HYBRID AND MULTI-CLOUD be synchronous while the majority
of interactions, such as non-inline
One of the key benefits of migrating
transactions and data logging, are
applications to the cloud is the flexibility
asynchronous.
it affords, especially if you migrate to the
cloud in a way that is cloud-native and
cloud-agnostic.
In many cases, these asynchronous proprietary, which can lock applications in
messages simply can’t be lost. You need a and reduce portability.
way to guarantee delivery to all intended
With technology’s rapid evolution, you
recipients (even if something goes wrong
need the peace of mind that comes from
with the network or an application)
using open APIs and protocols such as
whether a given recipient is disconnected
AMQP, JMS, MQTT, REST and WebSocket.
or unable to keep up with the flow of
messages. This includes accommodating
bursts of data without overwhelming
8 GOVERNANCE

recipients or putting back-pressure on Governance is critical for integration at


publishers. scale—for the sake of satisfying service
Then there are situations when all level agreements, conforming with
recipients have consumed messages but corporate security policies, and ensuring
need them again weeks or months later compliance with industry and government
due to technical issues. In such cases you regulations.
need to be able to let these applications You need robust governance for visibility
“replay” messages. of events via cataloging, and you need to
Global distribution (and the limits of be able to “eavesdrop” on events flowing
physics) dictate that not all endpoints will through your enterprise.
have the same data at the same time. This
is only acceptable if you are certain that
they will all eventually receive the same
events and therefore share the same state.

This certainty can only be achieved with


an event distribution layer that guarantees
delivery of events to all endpoints.

AVOIDING API AND PROTOCOL LOCK-


7 IN THROUGH OPEN STANDARDS

Open standards keep you from getting


locked into any architectural decision,
communication protocol, cloud or event
broker. Most cloud-native services are

7 Upgrading Your ESB to Event-Driven iPaaS


HOW EVENT-ENABLED IPAAS UNLOCKS TRUE
DIGITAL TRANSFORMATION

IPaaS offerings from companies such as Companies of all sizes are using iPaaS
Dell Boomi, Informatica, Jitterbit, MuleSoft solutions to integrate a wide variety of
and SnapLogic are gaining a lot of traction on-premises and cloud-native applications,
in the integration space, and their adoption which generally encompass the following
is accelerating with the increasing four functions:
popularity of cloud-native deployments.

1. Adapters that enable connectivity via a variety of open and proprietary APIs and
protocols;

2. Transformation of payloads so systems can send and consume information in


familiar formats;

3. Orchestration of processes and transactions that span multiple applications; and,

4. The real-time distribution of events and information via messaging and/or


streaming.
COMMON IPAAS DESIGN PATTERNS

Many enterprises adopt a very simplistic API interactions get coupled.


approach to integration, as depicted in the
As depicted in the image above, as more
image above.
upstream and downstream systems
An ESB or iPaaS (or even an API Gateway) get added a point-to-point integration
is deployed. It has adapters to connect or mechanism becomes exponentially
proxy services from legacy and modern complex. This is especially true if the same
systems. These adapters could be File or messages/APIs need to be sent to multiple
Database or Oracle or SAP ERP. Sometimes downstream systems.
they could be cloud or SaaS adapters, such
ESBs, and iPaaS’s that use REST, have
as Salesforce or AWS S3.
service interactions that are tightly coupled,
Once the connectivity is established with which leads to a lack of flexibility. Agility
the enterprise systems, transformations is also inhibited by orchestration (the
of payload is sometimes required. The codification of routing rules in BPEL or a
ESB/iPaaS orchestrates these services in a similar expression) as it requires someone
tightly coupled manner. to revisit the code each time an endpoint is
changed or a new one is added.
A simple point-to-point, RESTful
architecture works at a small scale, but as Adding new endpoints is difficult, and
more enterprise systems are connected, supporting many endpoints in this manner
agility and performance both suffer as the is inefficient.

9 Upgrading Your ESB to Event-Driven iPaaS


ENTER THE ADVANCED EVENT BROKER
As systems become more complex or scale possible latency and the need to ensure
in volume, an event-driven architecture lossless delivery no matter what. This
works much better. Fortunately, most includes the ability to ensure delivery
ESB and iPaaS offerings let you decouple to disconnected or slow consumers
applications and incorporate events without putting any back-pressure on
into the infrastructure by leveraging an publishing systems;
advanced event broker as the foundation
• Ability to link systems using open APIs
of data sharing behind the scenes.
and communication protocols such as
The core capabilities and characteristics of AMQP, MQTT, REST, JMS and WebSocket
advanced event brokers are: to make sure each application can use
an appropriate protocol;
• Support for synchronous and
asynchronous communications using • Support for sophisticated event routing
message exchange patterns such as and choreography, including the use of
publish/subscribe, queueing, request/ wildcards for messaging topics (MQTT,
reply and streaming; JMS, AMQP) and REST URLs. As an
example, you could publish REST and
• Support for best-effort and guaranteed
consume JMS/AMQP with the REST URL
delivery depending on the nature of the
becoming the JMS topic; and,
interaction, such as the need for lowest
• Governance capabilities such as security,
access control, event cataloging, metrics
and instrumentation.

REASON #5 FROM 7
WARNING SIGNS YOU NEED
TO REPLACE YOUR ESB:

“You spend more money on servers

and software than on modernizing your

infrastructure.”
Source: Dell Boomi
HOW TO EVENT-ENABLE YOUR IPAAS WITH
AN ADVANCED EVENT BROKER

Now let’s talk about why and how you advanced event broker to handle the high-
can take things to the next level by speed, high-volume distribution of events
incorporating an advanced event broker between globally-distributed applications,
into your iPaaS architecture. devices and nodes of your iPaaS.

Simply put, you’ll be using your iPaaS Here’s what you should strive to achieve as
for frontline integration, application you event-enable your iPaaS as a means of
connectivity, service choreography, and realizing true digital transformation.
message transformation, and using an

DECOUPLE SYSTEMS THROUGH SUBSCRIPTIONS

Agility is king. If you aren’t agile, you won’t synchronous request/reply interactions
be competitive. Building applications as a tightly couple services.
collection of cloud-based and on-premises
If someone needs to define, encode, test
microservices is a great way to make your
and deploy specific paths for information
IT infrastructure more agile, but tight
to take, they won’t be able to quickly adapt
coupling between these microservices
to new requirements. An event-driven
through request/reply-based synchronous
architecture lets new services participate
interactions can keep you from realizing
in existing flows dynamically, without
those improvements.
encoding or deploying any rules.
That’s because event-driven architectures
Traditional ESB orchestration involves
generally enable the loose coupling
codifying service interactions in
of microservices, while traditional
technologies such as BPEL, which means a

11 Upgrading Your ESB to Event-Driven iPaaS


series of services are tightly bound to one Likewise, using self-choreographed service
another. In order to add new producers interactions differs from orchestration
and new consumers of data, you need to in that failures cannot be compensated/
revisit the BPEL or, as with orchestration, retried. Guaranteed delivery offsets this
add the new endpoints, then save, test, and change in capability by ensuring eventual
deploy them. consistency.

That process is the opposite of To maximize agility, you must be able


dynamic, and applies to using REST in a to dynamically produce events and to
microservices environment as well. dynamically express interest in events.
With some event brokers it takes several
One of the benefits of synchronous
steps to create topics, and they limit or
interactions is you know if the endpoint
even prevent the use of wildcard-based
received the request, and you can resend
subscriptions. You also need to have
if required. Likewise, in orchestrated
the ability to have “queues” subscribe to
interactions, failures can be tracked and
events, as multiple events on topics could
handled with actions such as retries and
be funnelled into a queue to feed the same
compensating transactions.
microservices group in a load-balanced
When you switch to asynchronous manner.
interactions, the requestor/producer has
In short, you need both queuing and
no idea if the consumer received the data.
streaming, not one or the other.

BRIDGE SYNCHRONOUS AND ASYNCHRONOUS


INTERACTIONS
Modern architectures demand that However, synchronous exchanges are not
systems be able to communicate both going away; they’re still relevant for exposing
synchronously and asynchronously. external APIs, issuing commands and sending
Event-driven architectures are uniquely queries, to name a few use cases.
well-suited to meeting the needs of
A well-designed advanced event broker
asynchronous exchanges of data thanks
supports both synchronous and
to features including deferred execution,
asynchronous communications, enabling
parallel processing, and publish/subscribe
seamless bridging between the two kinds of
distribution.
communications.
CASE STUDY: CONSUMER PACKAGED GOODS
COMPANY

One of the world’s leading consumer that would exist in their new architecture.
products companies wanted to reduce Generally speaking, they needed to
costs and improve corporate agility overcome many of the challenges described
by consolidating over 60 datacenters above:
around the world into just 15 by migrating
1. They needed to establish extremely
applications and workloads to the cloud.
reliable and real-time event-driven
They relied on TIBCO BusinessWorks as an communications between systems
on-premises ESB to integrate applications, running in a variety of cloud and on-
and TIBCO Enterprise Message Service premises environments, commonly
(EMS) for queueing, routing, transportation called hybrid cloud and multi-cloud
and persistence of information between a architecture. Complicating this hybrid
powerful SAP ERP system and a plethora of cloud connectivity is that the number
supporting 3rd-party applications. of producers of data is unknown and
constantly changing, as is the number
To meet their goal of migrating workloads
of consumers of data, which can include
from datacenters to the cloud, the
cloud and on-prem destinations such as
company selected Dell Boomi to give their
AWS S3, Hadoop, Postgres and SAP.
cloud-native systems and services easy
access to capabilities such as connectivity, 2. They needed to integrate legacy
transformation, orchestration and error applications with IoT devices and
handling, all of which Boomi provides for microservices, and do so in a way that
both on-premises and cloud-native systems. enabled gradual migration both from
datacenter to cloud, and from batch-
From there the company needed a way
based to event-driven.
to connect the different service endpoints
13 Upgrading Your ESB to Event-Driven iPaaS
3. They needed to ensure rapid, reliable, The first application was to synchronize a
guaranteed delivery over very long master data management (MDM) system
distances (the Internet and private across various internal and external
WANs), factoring for long and less applications in two public clouds (AWS and
consistent round trip times, less Azure) and an on-premises system of record
predictable availability, and the need to as diagrammed below.
minimize/optimize bandwidth.
Batch data was also transformed into
Using the combination of Dell Boomi and streams at source, so consumers could
Solace PubSub+, the company was able consume a filtered stream on what they
to deploy a hybrid and multi-cloud event needed via wildcarded topic routing.
distribution backbone for gradually moving
apps to the cloud.
Given this architecture and associated devices only need to publish data to a local
operational requirements, they needed the Solace node. From there, AWS analytics can
SAP MDM system to be able to distribute consume it locally in the cloud either via
data to downstream SaaS applications. And subscriptions or a RESTful push.
as more and more applications were being
The company is now looking to build
spun up in the cloud, they needed the
a global event mesh on this same
ability to easily fan-out data to many new
infrastructure so they can publish in one
destinations.
region and fan-out to all the others. This
They utilized an event-driven architecture could very well be a many-to-many data
and the publish/subscribe exchange exchange, made easy with Boomi providing
pattern to decouple senders and receivers, integration and application services and
allowing for the very fast subscription- Solace ensuring the real-time guaranteed
based addition of new destinations. delivery.

Beyond the master data management While a current Managed File Transfer
application, many other applications—such solution can provide the data movement,
as order management, order processing, it is unable to offer the granularity,
and customer channel integration— self-routing, real-time, and protocol
leveraged the same event-driven iPaaS. independence of a Solace/Boomi event-
driven iPaaS implementation. For that to
The company also needed to give
happen, bidirectional data delivery, which
applications and devices the ability to send
Solace PubSub+ natively supports, would
and receive messages using JMS and REST,
need to be coded into MFT-style solutions.
both of which are supported by Solace
PubSub+. And because they plan to use
this same infrastructure as the foundation
of an IoT platform, they needed support for
MQTT, which PubSub+ also supports.

At the company, data is acquired from the


sensors on the factory floors that collect
information such as temperature and
running time. That data is then sent to AWS
for analysis and then sent back for action
to be taken. Thanks to the event-driven
architecture Solace PubSub+ enables,

15 Upgrading Your ESB to Event-Driven iPaaS


CONCLUSION
As made clear by the example above, pursuing a digital transformation can both solve
immediate challenges and allow enterprise leaders to cast their gaze toward the future.

This shift in mindset is what Gartner refers to as “event thinking(3)” and it’s critical for
enabling modern data integration and data movement across distributed enterprises.

Combining the easy, flexible, cloud-native integration that iPaaS offerings provide with
an event-driven architecture is the only way to achieve the maximum value from cloud-
native applications, hybrid cloud deployments, and microservices.

Endnotes

1. GARTNER “TOP 10 STRATEGIC TECHNOLOGY TRENDS FOR 2018: EVENT-DRIVEN MODEL.”


8 MARCH 2018, YEFIM NATIS, DAVID CEARLEY, MIKE WALKER, BRIAN BURKE.

2. “GARTNER SAYS WORLDWIDE APPLICATION INFRASTRUCTURE AND MIDDLEWARE MAR-


KET GREW 12 PERCENT IN 2017.” 4 JUNE 2018. HTTPS://WWW.GARTNER.COM/NEWSROOM/
ID/3877263

3. GARTNER “INNOVATION INSIGHT FOR EVENT THINKING.” 5 OCTOBER 2018. YEFIM NATIS,
ROY SCHULTE, ROB DUNIE, ELIZABETH GOLLUSCIO.

16 Upgrading Your ESB to Event-Driven iPaaS


ABOUT SOLACE
We are the creators of PubSub+, an advanced event broker that can
be used to create an event mesh. As the only unified event broker that
supports publish/subscribe, queuing, request-reply and streaming using
open protocols and APIs across hybrid cloud and IoT environments,
PubSub+ rapidly and reliably routes information between applications,
devices and people across clouds. Established enterprises such as SAP,
Barclays, and the Royal Bank of Canada as well as high-growth companies
such as VoiceBase and Jio use our smart data movement technologies to
modernize legacy applications and successfully pursue analytics, hybrid
cloud and IoT strategies. Learn more at solace.com.

A FEW OF OUR CUSTOMERS

OUR FEATURED PARTNERS

R
solace.com

Оценить