Game-changing technologies are hard to come by, the reason being that they need to fundamentally alter the way people look at things. And needless to say, it’s hard to alter things that have been proven and tested. In my blog on Why the Integration Market Is Ripe for Disruption, I discussed how the world around us is changing and that there is a specific need for new approaches to integration. As a next step, I will be doing a series of blog posts on how IT needs to perceive integration in this new world, and today I’m going to discuss Snaplex.
I regard Snaplex as one of those key agents of change/disruption in the world of integration. Let?s look at how Snaplex is different and what you need to know about it in in order to start looking at your integrations differently:
An Elastic Execution Network
Amazon EC2 (Elastic Cloud Compute) delivers unlimited scale to applications running on top of it and the SnapLogic Integration Cloud delivers on unlimited scale to integration flows, something that I’ve referred to as the final frontier of elasticity in one of my previous blog posts. The Snaplex is the data processing engine of the SnapLogic integration platform as a service (iPaaS). Although the design and administration components are multi-tenant or shared across customers, each customer gets a dedicated Snaplex for processing their data. All Cloud Snaplexes run in the same SnapLogic cloud. The on-premise Snaplexes run on private data centers and behind the firewall.
Each Snaplex can elastically expand and contract based on data traffic flowing through it. The unit of scalability inside Snaplex is a JVM. The SnapLogic Integration Cloud has built-in smarts to automatically scale the Snaplex out and in to handle variable traffic loads. For instance, each Snaplex is initialized with a preconfigured number of JVMs (say one, for example). Once the utilization of that one JVM reaches a certain threshold (say 80%), a new JVM is automatically spun up to handle any additional workload. Once this excess data traffic has been processed and the second JVM is sitting idle, it gets torn down to scale back in to its original size.
Such elasticity can be appropriated in public as well as private clouds.
One of the great benefits of using a SaaS product is that you, the customer, no longer need to suffer through painful and costly software upgrades. You no longer have to wait years before newer versions of software are available, and you are automatically upgraded to the latest code on a frequent basis. You can also do away with costly cycles of installing, configuring, and testing new versions of software. And you no longer have to worry about migrating from old product to new, as the cloud vendors assume that responsibility.
You are probably wondering whether this self-upgrade story is applicable to the on-premise Snaplex. The answer is a resounding yes. Even the on-premise Snaplex can be enabled to be automatically upgraded to the latest bits. However, you do have the option of turning off the automated upgrade.
On-premise and Cloud parity
Cloud integration is certainly not a new topic. There are many cloud integration vendors that offer integrations across SaaS applications. They have built competency around the cloud-to-cloud integrations. The legacy integration vendors that started off in the on-premise world have done an effective job of integrating on-premise applications and are now cloud-washing their products by providing lightweight agents to connect into the cloud. No vendor, until now, has been able to deliver parity in terms of robustness, scale, processing, power, SaaS-yness across on-premise and cloud, for the hybrid realities of the world.
Snaplex delivers on just that by offering a single set of code that executes on-premise as well as the cloud. One of the benefits of this approach is that you no longer have to worry about two sets of adapters/connectors that some of the cloud-washed vendors will make you do (depending upon whether you are deploying in the cloud or on-premise). You no longer need to worry about two sets of management and administrative consoles or activities. In many ways, SnapLogic is solving a problem that was artificially created because of our historical approach to solving integrations.
Coming back to how this innovation will help you look at integration differently, with the SnapLogic Integration Cloud:
You no longer need to buy hardware and software for that black swan scenario when traffic will spike 10x and your servers? inability to handle it to cause business downtime.
You no longer need to force-fit a tool (EAI vs ETL) to solve an application or data integration problem. You can use an elastic solution that can handle both patterns and workloads (ref: the Integrator’s Dilemma).
You no longer need to worry about costly and painful software upgrades. You now move at the pace of innovation of a Silicon Valley start-up.
- You no longer need to worry about where the data is (whether on-premise or in the cloud), and you can flexibly and uniformly access that data with a single set of tools and single set of connectors. Now, you can truly focus on the business problem at hand, and not get entangled into the complexities of the tool you need to use.