Webinar: Crowd Release – Intro to Anypoint Exchange & API Designer [Demo]

crowd mulesoft

The Crowd release, the next major release of Anypoint Platform, harnesses powerful collaboration capabilities and allows users to build, save, discover, and reuse APIs and other integration assets within the platform. These capabilities enable organizations to build application networks faster by making the design, discovery, and reuse of IT assets simple and intuitive.

To introduce you to the Crowd release and the above capabilities, we have 2 upcoming webinars.

Advanced API Patterns with RAML

advanced raml design

The vast majority of RESTful APIs follow a simple “request-response” message exchange pattern, but that pattern is often too limiting and is not sufficient to achieving robust and reliable application performance.  We frequently get questions from customers asking:  ‘How I design asynchronous APIs?’ and ‘How I design an API that allows for the concurrent modification of the same API resource without bringing the resource into inconsistent state?’.  In this blog post, we present two approaches answering these questions using standard HTTP headers and status codes.

Anypoint Studio 6.1 Release: Enhanced API Development Support

August 24 2016

2 comments
anypoint studio logo

About three months ago, we released Studio 6.0, which was a significant step towards covering all API-related use cases in one single design environment. Since then, almost half of our active users have embraced Studio 6.x, to define, create, consume and test APIs. Now, we are excited to release Studio 6.1 as another step to make Studio the most powerful and productive API development and integration tool.

RAMLing again with API Workbench: From setup to design

I previously published a blog post in DZone that demonstrated how to design a RAML in API Designer, which is an online cloud editor that uses an in-browser filesystem in HTML5 Local storage. But then I thought of exploring some more options for a tool/editor that can help us to design and code our RAML locally as an IDE (such as Eclipse or Netbean for Java).

API Best Practices: Spec Driven Development (Part 2)

November 20 2014

0 comments

This is part two of the API design best practices series.

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.

The Real World Cup Winner: APIs

motif

What a world cup! I do feel bad for 50% of the MuleSoft team though (given that we’ve got a big office in Buenos Aires). It’s exciting though, because this was a very exhilarating competition that truly reached a fever pitch here in the US where “football” is traditionally a game with pads, helmets, and ball that doesn’t really roll.

What was really interesting was how this was truly a, “World Cup powered by APIs.”