Java Message Service Built For The Cloud: An Introduction to TIBCO EMS X
Blog: The Tibco Blog
Reading Time: 3 minutes
If there’s one concept dominating the enterprise software world today, it’s cloud migration. But the term “cloud migration” glosses over some of the complexity in adopting a cloud-centric approach. No matter who you talk to in the enterprise software industry, the whole concept of moving to the cloud seems to be simple. But is it really as simple as we like to frame it?
One of the biggest challenges we face when we discuss migration to the cloud is terminology. The word “migration” brings to mind a natural process that happens regularly, out of necessity. For example, here in the midwestern United States, Canadian geese fly south for the winter every year. Yet they lack the capacity to take flight across a single road, leaving motorists to wait, watch, and blare their horns in frustration as the geese lumber slowly through the streets.
Bird migration seems so natural, carefree, and seamless that we take it for granted. Just like a leaf’s seasonal color change, the natural process of migration seems to just happen without any effort. However, for the birds, migration is a process that they plan and coordinate every year.
The birds prepare by coordinating where and how they will travel. They also plan for access to food well in advance of the migration so that they’re nourished and capable of handling the long flights ahead. So, what seems seamless to the outside observer is actually carefully planned and coordinated to maximize energy, efficiency, and survival.
We sometimes look at the migration of enterprise applications and workflows as a natural, seamless event that occurs without any preparation or planning. But in fact, moving on-premises applications to the cloud takes effort, planning, and coordination—and, more often than not, it requires a “lift and shift” approach, which incurs downtime and lost productivity. Even if a “lift and shift” approach is possible, organizations still need to move specific applications selectively, which requires coordination and planning.
Avoid Downtime When Moving to the Cloud
TIBCO Enterprise Message Service
X (EMS X), TIBCO Cloud Messaging 4.0, and TIBCO Cloud Integration (TCI) 3.3 converge to simplify migration coordination and planning. Together, these solutions provide a more seamless way to migrate traditional enterprise applications from on-premises estates to modern cloud architectures—without having to incur the hard stop that a “lift and shift ” approach requires. TIBCO’s approach centers around a tightly coupled, cloud-first strategy, providing the capabilities required for enterprise integration to seamlessly move and integrate with both on-premise and cloud-based deployments.
The first layer of TIBCO’s solution focuses on TIBCO EMS, with the introduction of TIBCO EMS X and two new storage approaches that are built and designed for ease of deployment in the cloud. With TIBCO EMS X, the TIBCO EMS infrastructure can be deployed using either the traditional file-based shared storage model or one of two new non-shared storage models—either TIBCO FTL® Cluster Storage or TIBCO ActiveSpaces® Data Grid storage.
Both new non-shared storage models provide simplified cloud deployments and remove the requirements for third-party storage hardware and software—while also providing long-term data storage (TIBCO ActiveSpaces Data Grid storage) or high-performance in-memory message persistence (TIBCO FTL Cluster Storage).
With these new non-shared storage options, solutions built to use TIBCO EMS on-premise can take the initial steps for cloud migration by transitioning to these new storage options in preparation for moving the EMS infrastructure to cloud-based deployment.
A Path to the Cloud for EMS Workloads
TIBCO Cloud Messaging 4.0 leverages TIBCO EMS X for the newly introduced communications channel supporting TIBCO EMS. With the introduction of TIBCO EMS as a function of TIBCO Cloud Messaging, the migration to cloud is even easier with a fully managed option provided natively on TIBCO’s managed cloud.
In addition, with the introduction of TIBCO Cloud Integration 3.3, enterprise integration applications can now tap into multiple EMS datastreams and provide a seamless approach to integration. With TIBCO EMS X, TIBCO Cloud Messaging 4.0, and TIBCO Cloud Integration 3.3, some of the largest enterprise integration applications that have been built on a proven heritage of TIBCO BusinessWorks can now make the migration to cloud without having to take that “lift and shift approach.” Enterprise estates can continue to leverage their existing investment in TIBCO EMS and TIBCO BusinessWorks and route data to newly deployed cloud architectures, using TIBCO EMS X or TIBCO Cloud Messaging 4.0—incorporating new functionality with TIBCO Cloud Integration.
This flexible approach to infrastructure allows the right data to be in the right place at the right time. Now, with the introduction of new non-shared storage options for EMS X and the ability to leverage those storage options as a part of TIBCO Cloud Messaging, integration applications can leverage their past to build on their future without compromise.
For more information on which storage options for TIBCO EMS X are right for you, read this TIBCO Enterprise Storage Options whitepaper.
The post Java Message Service Built For The Cloud: An Introduction to TIBCO EMS X first appeared on The TIBCO Blog.
Leave a Comment
You must be logged in to post a comment.
