APIs are becoming critical to thriving in today’s digital economy. In our recent Connectivity Benchmark Report, we surveyed over 650 IT leaders and found that businesses across industries are realizing great benefits from APIs. This includes increased productivity (58%), increased innovation (48%), and increased employee engagement (43%).
API response time is essential to providing the frictionless end-user experiences necessary for you to meet your API program’s KPIs and retention goals. One way to optimize performance is by having a caching layer in your API architecture. This layer allows you to deliver cached responses for common requests––thereby accessing data in a quick and inexpensive manner.
Last fall we wrote an article that examined which APIs draw the most interest from developers. In that article we relied upon the API tracking functionality that each profile has as the metric for determining which APIs are the most popular. As many users of ProgrammableWeb know, reader’s can track any asset on ProgrammableWeb.com (APIs, SDKs, even search results) in the same way they can track stocks on a financial site. If anything new happens to that asset (if it gets updated,
User management and provisioning have always been tedious and time-consuming tasks for IT professionals. If you’ve seen any of my blog posts before, you’ll know that there are two things I like: exposés in the form of parentheses and removing tedious manual work.
Naturally, this meant I ended up trying to solve user management. One of the first questions I asked when I started addressing this problem was: why hasn’t this been solved yet?
Previously, I wrote a blog post about IT Engineering here at MuleSoft and how we use MuleSoft products at MuleSoft. Inter-team communication is critical for us to complete projects and we decided to implement a Center for Enablement (C4E) approach internally. The MuleSoft customer success team offered to assist us in pursuing an evolved approach to developing MuleSoft applications for IT.
Recently, the RAML team decided it was time for an updated server infrastructure. The original site used a web-based Content Management System (CMS) that required a lot of costly server resources. Each client request to the CMS invoked scripts that rendered the pages from outside sources, such as the database and theme;
This led to significant processing time before providing what was, in most cases, a static page. Of course, we ran a caching layer in front of the web server to speed up some requests,
During my time at MuleSoft, I’ve had a lot of conversations with people from other companies about their specific challenges and one recurring theme is almost always present: the conversation starts out talking about point-to-point integrations. It’s pretty natural when presented with two systems to want to draw a connection. The data here is needed there and, after that, we’re done because a problem was solved.
What is the difference between web APIs and web services? Let’s start off with an analogy: all tigers are cats but not all cats are tigers. In a similar way, all web services are APIs, but not all APIs are web services. Web APIs and web services are often confused with each other; however, web APIs are an evolution of web services. Both facilitate information transfer, but web APIs are more dynamic than web services are.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.