Integration + Cloud: A Match Made in Heaven
Blog: The Tibco Blog
Last year on February 14th we published a blog post on “Building the Ultimate Valentine’s API.” Personally, I had a lot of fun writing it and finding facts related to how we spend our Valentine’s Day (though I forgot to bring home chocolates and flowers to my wife, who was none too pleased)! To prevent history from repeating itself, we’re taking things a step further this year with a Valentine’s Day webinar on why Integration + Cloud = A Match Made in Heaven.
Some fun stats on Valentine’s Day: For this holiday, florists produce about 198 million roses, send 180 million cards—and there are about 1,200 locations producing chocolate and other cocoa products for us to give to our loved ones. [1]
Speaking of love, I believe that every developer has that one special technology they absolutely love—whether it’s a programming language (like Golang, Java, or Node.js), an architecture style (like microservices and APIs), or simply all sorts of open source software. TIBCO holds this belief as well, so we decided to put it all together in one easy to use place. Putting it in one place doesn’t mean you have to use our cloud to deploy this tech—you can choose to deploy it on-premises, to a private cloud, to devices, or to serverless environments. Talk about an open relationship! 
In the webinar, we’ll touch on three essential elements that create a healthy and strong bond between integration and the cloud. We’ll talk about rapidly prototyping apps and APIs, choosing where you want to deploy those apps, and how you can keep using the same app model when you’re moving between environments.
To rapidly prototype APIs you’ll need to look at two incredibly important aspects. First of all, you want to be able to visually create those API specs. This is really important because not everyone will be able to write an Open API spec (formerly known as Swagger) from scratch, using nothing more than a text editor. The second important thing is the ability to test your API specs before you hand them over to a developer, or implement them yourself. Testing in this early stage is really important because it allows you to see whether the inputs, outputs, and operations match with your design. Plus, it gives other developers the chance to start writing their integrations while you focus on the business logic.
The Greek philosopher Heraclitus is credited to have said, “Change is the only constant in life,” and I would assume that if he observed the modern world of integration technology, he would have said the same for it. As we move from seeing ESB and iPaaS as only a method to connect applications to each other and move towards those technologies being the infrastructure on which modern apps are built, you can see the lines between application development and integration rapidly blurring. We’re moving from big monolithic apps to containers and functions, and we’re adopting lots of new patterns like Function-as-a-Service, evented APIs, and microgateways.
The last item is all about choice, one of the most important things in dating, and in integration as well. When you’re working on your integration or application development project, you might not know where you’ll end up deploying it. The code might end up on Kubernetes, in the TIBCO Cloud, or on-premises. Because you already have so many choices to make when you’re building, you don’t want to have to migrate when you’re moving to a different environment. You want to be able to take your app and deploy it somewhere else!
As Charles M. Schultz once said, “All you need is love. But a little chocolate now and then doesn’t hurt.” So, I should probably stop writing this blog and go get my Valentine some chocolate. If you want to get started with TIBCO Cloud Integration, you can do that here, or go sign-up to attend tomorrow’s webinar. The best news? Even if you stand us up, you’ll receive a copy of the recording.
References:
Leave a Comment
You must be logged in to post a comment.
