Microservices on rails

railroad tracks

In the intro to this blog series, I promised to reconcile the apparent incongruence of strategic business objectives (move fast) with traditional IT must have paradigms (be safe). In the last post, we chugged away at the surrounding ecosystem that’s needed to support the velocity promised by the former. In this post, I pause at the pre-production station to discuss some of those system safety properties that we can’t leave behind.

Code reviews and code craftsmanship at MuleSoft

developer writing code

As engineers, much of the quality of our days and lives depends upon the quality of the codebases on which we work.

The present future of APIs in the business

apis future

What is IT’s role in supporting the business? Is it to create the technical processes that allow work to take place? Is it to perform the logistical and operations tasks that document processes? I believe that IT should be a strategic, rather than a wholly operational function. For that to happen, though, we need to focus on how to abstract away the complexity of IT operations. The value of abstraction is simple: abstraction allows us to move faster and focus on business objectives rather than on logistics and operations.

Three common API design mistakes and how to overcome them

apis

Jason Harmon, head of APIs at engaging forms tool Typeform, and namesake of the JSON schema, gave a fantastic proactive talk at a recent APIdays conference about “the things that break stuff in production.” Three things in fact.

Common API mistakes

common api mistakes

Do you know if you are doing it right?

This is the question that many of us are faced with when starting with APIs, and quite invariably, there would be either of two broad scenarios that we generally find ourselves in. We are either starting green field under the clear blue sky with every little thing to elicit, introspect, and design; or else we are in a continuum, trying to understand the current system,

5 Things You Need to Know About Crowd

crowd release

Over the past few months, I have been working with our Product and Engineering team on Crowd, the latest release of Anypoint Platform. The Crowd release consists of updates to Anypoint Exchange as well as the new Anypoint Designer Center in Anypoint Platform.

Anypoint Studio 6.0: Bringing together capabilities across the API development lifecycle

motif

As part of our Anypoint Platform June 2016 announcement, we are excited to release Anypoint Studio 6.0. We know API development, system orchestration and connectivity are increasingly intertwined tasks. This release is all about unification — with a goal of making our users even more productive in accomplishing these tasks.  Anypoint Studio 6.0 provides everything you need to design and build APIs in a single,

HowTo – REST API proxy to SOAP webservice

This blog post is a continuation of our first How To series, “APIFy your integrations,” where we started off by creating a SOAP API around a database.

Some organizations are entirely invested in either SOAP or RESTful web services. There is plenty of material already written on SOAP vs. REST, so there’s no need for us to take that on here.

It can be a use case driven decision where SOAP and REST can co-exist.

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.

Analytics – The new currency of the API economy

motif

By unleashing your digital assets, developers flock to consume the digital mana, creating new value for consumers in the API age. The proliferation of both open and closed APIs has created a rich diverse ecosystem which is driving the Internet of Things (IoT) from an idea to a reality. But how do you get the most out of your existing APIs, and/or create new ones nimbly?