Mike Stowe on Thursday, December 18, 2014

API Best Practices: Hypermedia (Part 2)


Part four of the API design best practices series. Read part one: Plan Your API.

Or jump to part one of the hypermedia sub-series.

The Harsh Reality of the State of Hypermedia Specs

Hypermedia sounds great in theory, but theory only goes so far. Where really shines, or completely fails, is in implementation. Unfortunately, as is still a relatively new aspect of web based APIs, there isn’t one specified way of doing things. In fact, you’ll find that even some of the most popular APIs operate completely differently from each other.

Mike Stowe on Thursday, December 11, 2014

API Best Practices: Hypermedia (Part 1)


Part four of the API design best practices series. Read part one: Plan Your API.

What is Hypermedia

One of the challenges to implementing and correctly using in your API is first understanding what hypermedia is, and what it means to use hypermedia as the engine of application state (HATEOAS).

Financial services information technology (IT) has transformed from order taker to strategic business partner. As part of this transformation, IT organizations are finding they must address key challenges with legacy modernization, data management and digital transformation.

MuleSoft has launched a three-part white paper discussing these challenges and how financial institutions are overcoming them. In the first installment in our Connected Financial Institution whitepaper series, we discussed how aging back office systems, operational effectiveness and open source adoption are driving legacy modernization initiatives across the financial services industry. But the story doesn’t stop there. Modernizing legacy systems is only the first step in addressing the business imperatives faced by financial institutions.

Part three of the API design best practices .

Once you have an understanding of what your API needs to be able to do in order to meet your developer’s requirements, it’s important to ensure that it remains as flexible and extendable as possible.  Taking advantage of best practices not only means that your API will be familiar to developers, but also ensure that it remains fluid enough to extend and build on top of it in the future.  Here are this week’s best practices to help keep your API agile:

always matters

An application and its environment should be designed with performance in mind. The application, the server it runs on, the database it communicates with, the network it communicates over: all of these elements should be performant. Creating an efficient, elegant mechanism is not only important for a business, but a matter of skill and pride for engineers.

Although true, perhaps that is not the answer one is looking for. When does performance matter? is too broad. The following discussion helps clarify the question, how to answer it, and what to do about it.

Priya Sony on Tuesday, December 2, 2014

API Meetup Premieres in Argentina


APIs proudly made in Argentina

A couple weeks ago the first APIsAR meetup took place at MuleSoft’s Buenos Aires offices, with MuleSoft as one of the sponsors.

(APIs Argentina) is the first and only Argentine community focused on discussing the world of APIs. “The community was officially launched on September 9th,” commented Norberto Herz (founder of APIsAR) and at the time of the event, “it has more than 300 hundred members, mostly from Argentina, but also from other Latin American countries, as well as Spain.

The event agenda included a half an hour welcome reception, followed by an hour of talks and presentations, closing with another hour dedicated to networking over food and drinks.

Millo Ognissanti on Wednesday, November 26, 2014

Thanks for connecting with MuleSoft!


Well, it’s that time of the year again! This is when we put our phones down (well, mostly) and give thanks for everything and everyone around us. We at MuleSoft have a lot and a lot of people to be thankful for. Business is going well (see our Record Q3 Performance announcement), we’re gaining industry recognitions (see our Awards page and in particular, the last Deloitte’s Technology Fast 500 ), and we keep growing. But it’s in times like these that we want to thank everybody who has helped us get where we are today. It’s our customers who believed in our products and always gave us their brutally honest feedback that allowed us to improve and make a better product. It’s all of the Muleys who have poured their energy day-in day-out in building this company and making our vision a reality. But I would like to take a few moments to thank some people who rarely get all the credit they deserve for the work they do: developers.

I am excited to announce that our November release of the Anypoint Platform for APIs is now live. This update to the platform includes a variety of new features and workflow enhancements aimed at streamlining the process of managing APIs. These new features include the following:

  • Improved proxy configuration & support for HTTPS and load balancer scenarios
  • API version deprecation
  • Swagger file import & folder support in API Designer
  • Analytic tracking of policy violations

Proxy Configuration Improvements

As part of the November release of the Anypoint Platform for APIs we have also released a new version of the API Gateway, version 1.3 which you can download here. The new API Gateway includes enhancements that now make it possible to easily deploy API proxies in a loadbalancer environment as well as use a shared port for HTTP and HTTPS endpoint. Shared ports allow you to deploy multiple API proxies to a single gateway. As a result, we’ve modified the proxy generation interface in the platform. Please note, that to take advantage of these new updates to the API proxies you will need to use the latest API Gateway version 1.3. To learn more about configuring and deploying proxies in the Anypoint Platform for APIs you can find full documentation here.

Part two of the API design best practices . Read part one: Plan Your API.

Define Your API in a Flexible, but Standard Spec

I cannot stress the importance of spec driven development enough.  One of the quickest ways to kill your API is to define the API in your code, instead of coding to its definition.  By utilizing an API modeling spec such as RAML you can quickly build out your API in a consistent manner using code and pattern reuse.

Utilizing pattern design and code reuse helps to ensure that your API remains uniform across the full interface, keeping resources and methods alike standardized and easily implemented by your developers.

Enterprise integration poses huge challenges for developers, and with so many tools and solutions to choose from, finding the right one can be tricky. DZone’s 2014 Guide to Enterprise Integration, their latest research and guide, provides coverage of the landspace and offers key insights from 500+ developers and experts. The guide considers web services, integration architecture, SOA governance, enterprise service bus products, message queues, integration frameworks and suites, iPaaS solutions, API management platforms and much more.

Topics covered in the guide include:

  • Integration Architecture: How We Got Here
  • Integrating Microservices Into The Enterprise
  • Decomposition Patterns for Monolithic Applications
  • The Future of Developing and Integrating Applications
  • Microservices: Taking a Closer Look
  • A checklist for “The API Maturity Model”
  • Beyond Traditional Enterprise Integration: Bi-Modal IT