With the rapidly increasing adoption of SaaS, integration Platform as a Service (iPaaS) has become the preferred way to connect SaaS applications. However, with the explosion of Open APIs on the Web connecting APIs together is becoming the norm for application development. However, typical application containers and even application PaaS offerings don’t help in this new era where applications compose APis together from many different sources.
In 2005 there were 105 open APIs. Today there are over 5,000. What does this mean for you and how you will build your applications? Join MuleSoft’s CTO Ross Mason for some insight into the implications of API proliferation.
We recently pushed out an update to iON which makes building APIs in the cloud better than ever: zero downtime upgrades. Without you having to do anything, we ensure that your application is able to continually serve requests while you’re updating it.
The way this works is simple. Let’s say you have version 1.0 of your application in production and you’re about to release version 2.0. Because version 2.0 may take a few moments to start,
Mule has a new really cool module ready to be used in Muleforge called Dynamic Flows. The idea behind this new module might sound strange at first but it is actually quite simple: it allows you to add new flows to your existing mule application without restarting the server. It provides three simple operations for flow management:
Creates a new mule context with the name and configuration provided.
Wondering what 2012 will bring for the IT world?
Ross Mason, MuleSoft Founder and CTO, has identified the five major trends you need to watch this year and how they will affect your organization. These trends are:
As cliché as it is to say, it’s hard to believe that an entire year has passed since I last took stock of Mule. When I look back on 2011, it’s absolutely incredible to me how far MuleSoft and the Mule community have come.
At QCon SF last week I gave my talk on DevOps to NoOps: 10 cloud services you should be using. I talked about what I call the API explosion and how that impacts the way we build applications before introducing my list. I focused on infrastructure APIs because I believe these have the biggest impact on application development and thus the developers that build applications.
Its about time the Web became more event-driven. We have had AJAX for many years enabling events between server and browser, but on the backend we are still polling data. With the explosion of public APIs from SaaS, Social Media and Infrastructure Apps, more and more applications are written by composing web APIs. Developers often need to call a API to get data updates, only to find that nothing has changed. Streaming APIs provide a more elegant solution to polling allowing developers to subscribe to changes they are interested in.
Working with web APIs, local APIs and different data formats and structures is too damn hard. You have to write painful verbose code to:
- Query Web APIs and work with the data
- Enrich and join data from external services with local services
- Compose RESTful services from existing services
- Version services and data formats
- Merge data from different sources into a common data format
- Sort through sets of data
There was a lot of buzz a few years ago around real-time web and since then it has been bubbling along. I have a financial/enterprise background so real-time has a very different meaning to me; time is measured in microseconds. Web real-time seems to be measured as sub 1 second . My issue with real time web to date is only parts of the web are web-real time. While the data can be delivered to the browser using push technologies such as comet and web sockets,