For the past six months, I worked on a federal consulting project to transform data from a client’s legacy systems into a new centralized cloud repository. We chose MuleSoft as the integration and API platform to drive this transformation. After implementing my first MuleSoft project in the federal space, I jotted down a handful of takeaways to share with others embarking on new projects. Here are my top learnings:
What is an API developer experience? It sounds similar to user experience (UX), right? Almost – API developer experience (DX) is the practice of understanding how developers work, and more importantly, optimizing the experience they have through the whole lifecycle of an API. The developer experience has lately evolved from user experience because it sees developers as a special — and unfortunately — underrated case of user. Creating a positive experience for your developers is about understanding the context of how they use APIs,
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.
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.
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.
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,
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.
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,
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.