I have read a lot of positive feedback coming from industry visionaries of TIBCO NOW 2016, including Sandy Kemsley and Ghislain Côté. While these cover the incredible announcements made by TIBCO at the event, what really exemplified the new TIBCO was the amazing sessions given by customers and partners that makes you really take a step back and think about how the integration landscape is changing and what you must consider. Failing to consider these and choosing a platform that does not address these points, may be a big step backward, jeopardizing your future success.
How does containerization change your approach to integration?
Listening to various breakout sessions from Allan Nima, Product Manager of Google Cloud Platform and David Potes, Partner Solutions Architect at Amazon Web Services, it is clear to me that containers are going to be a critical piece of any organization’s plans going forward, if they are not already. How will your integration platform fit into this emerging architectural approach?
What are the implications of 12-factor, cloud-native application design will have on your integration platforms?
Multi-tenancy, twelve-factor app design approaches have introduced new requirements when building your applications. Simply leveraging an Integration service in the cloud does not mean the applications you build with your integration platform will follow these methodologies, you need to examine you integration technology to see if you need to approach your application design differently or even if your integration technology will support these approaches.
What is the role of the iPaaS, in this new API-first world?
While cloud service integration is still critical, listening to Pandu Ranga Swamy Prudhivi from AppS Associates talk about their API driven, contract-first approach to simplifying time-to-market for their clients’ project, it is clear that this new API Economy will be changing how users approach solving connectivity problems. The iPaaS platforms will be required to evolve to support this shift in customers’ new API focus.
How do you deal with real-time, event-driven mobile integration requirements?
In sessions and interviews with both Amit Sachdeva and Mike Thompson of Kony, a leader in the enterprise mobility space, a number of integration patterns were identified where the request/reply nature of HTTP is not suitable in a mobile environment (e.x. full duplex bidirectional communication, high volume, guaranteed delivery requirement, etc.). Will your integration platform be able to leverage asynchronous communication out to mobile devices to support these integration patterns?
Dealing with challenges of the Internet of Things
Dealing with the integration of these millions, or even billions, of devices is not just simply providing the connectivity. The connectivity is certainly important, but because of the volumes and even constraints around network connectivity or bandwidth availability, it makes sense to move some of these integration requirements out to the devices, where certain logic can be applied, data consolidated, and as a result less frequent, more relevant communications take place, eliminating many of the constraining bottlenecks facing IoT projects today.
But you still have the challenges of dealing with the ever increasing volumes of information IoT will generate. To capture the value of this information, will your integration platform offer you real-time streaming event processing or will you need to bring on another tool to address these challenges and will your integration platform work well with it?
Who will need to perform integration work?
Historically, integration was done within the core IT function, by the Integration Centers of Excellence. The iPaaS offerings simplified the process of interconnecting cloud-based services allowing developers within the lines of business or even in smaller, less sophisticated organizations to perform integration tasks. That is not enough anymore. These days, success is about empowering every user in the organization to drive change and disrupt the status quo. The integration technology you leverage should support integration performed by people who do not know programing, or for that matter do not know what integration is. It is about empowering the digital citizens, who simply know they need to connect to services or devices and share information.
TIBCO and its customers and partners demonstrated this past week the next-generation of integration that addresses all the above and more. TIBCO delivers integration to on-premises, containers, or to cloud platforms. We provide the shortest path from the creation of an API to its publication. We integrate legacy, microservices, APIs, devices, you name it. TIBCO caters to the center of excellence, the line of business and digital citizens. We interconnect everything. Don’t let your integration step backwards. Discover the next step forward for your integration here.
Additionally, if you are at the Cloud Foundry Summit, May 23 – 25, 2016 in Santa Clara, California or the Gartner Application Architecture, Development & Integration Summit 23 – 24 May 2016 in London stop by and see the TIBCO technology first hand.