MuleSoft Ambassador Patryk's Blog
We are used to designing and exposing REST APIs using Design Center and Anypoint Exchange. MuleSoft is one of the leading middleware vendors that introduced the complete design life cycle. It helped a lot as the majority of the APIs are RESTs. On the other hand, we have event-driven APIs using queues, streams, sockets. So…
New Anypoint Studio 7.5 came with an exiting feature. From now on, we can design our APIs in Studio instead of the Design Center. In this article, you will see how it works and how to use it. Let’s see if this can improve our day-to-day tasks. Create an API The first step must be…
Raml 1.0 introduces new concept called DataType. This fragment is used to declare type in a separate yaml file. This is not just a simplification of JSON schema to conform raml/yaml. It also brings simple improvements and syntax sugar that allows to write types in more concise form. And therefore more readable. In this article we will look at how to define own data types and reuse them in API and its implementation
HTTP GET method’s simple design has been published in a previous article. I designed the account service using the RAML specification. It is time, now, to implement that service so our potential users could consume it. To implement the service I use Flow Designer available on Anypoint Platform. To follow my steps you wouldn’t need…
This article is an intro to a blog series about HTTP methods usage in RESTful services. As a GET is the most common, I will start with it. This method is used for retrieving the collection of resources or a single resource. In other words, GET can be used for searching purposes. However, the more…
