Pass Mulesoft MCD - Level 1 Exam in First Attempt Easily

Introduction

1. Setting up your PC and Use Case

To get started, you need three things. The first one is java SDK Eight you can come on this website, choose your flavor, download and install tithe second thing you want is is any point studio. Seven, you can go on this viewport’s website. You can download a 30-day free trial. You can choose your operating system and download tithe third thing which you need is any point platform. This will help us to design Apiece, deploy mule applications and look at other things available on the endpoint platform. All the links which I showed you will be available on this GitHub repository. Now let's look at what the use cases. We are going to be focusing on creating mutes of space program. We’ll be having planets information. We will be talking about how to long launcher, rocket and the space in general.

Hide

Application Network

1. Application Network

One of the problems in It is that pre 2015it was evaluating about mobile cloud Iota and other applications. Now it's impossible limiting it’s what is happening is the depth of understanding each of these terms is deepening. It is super hard to manage the tangent and so the demand is increasing. Some of the solutions could be yes, we can do code reuse, we can have better integrations, we can have more innovations in this, we need to have faster Iterative deliverables, agile, can ban, we can have APS connectivity approach. There are many solutions. Before we try to figure out what the solution is, let me tell you a story. Let’s say a person goes to a restaurant, he looks at the menu, he knows what he wants to have. He asks the waiter to get him a certain kind of food. The waiter goes to the kitchen, brings him food, and he's happy. Now, to understand what is happening in this story is that the person who came into eat is actually a consumer. He looked at the menu, which you can think of it as an API specification. The kitchen could be a resource. So from the menu, he's looking at what you can order from the kitchen. So you can think of that as a system of record. And the waiter who's delivering all of this is actually a middleware. You can think of it as an Apies what is an API? It's an application programming interface. It’s a software intermediary which allows two applications to talk to each other. Now, would you ask, what does the modern API include? Rest and HTTP are opinionated standards. We treat modern APIs as products rather than just source code. They are very well documented and very, very easy to understand. The consumption is very simple, and there are versions to understand KPIs or modern APIs have a lifecycle.

2. REST and SOAP

Whenever we talk about APIs, people often get confused between Rest and So. There is no direct comparison between Rest and So because you need to have apples topples comparison to do it perfectly. Let’s talk about rest first. It’s representational state transfer. It’s an architecture style to provide a standard for communication. There are certain rules like client service separation, statelessness and caching. Whereas soap is a protocol. You can think of it as an example which provides some features, for example web service security, complex transaction handling, asset compliance and also has a logic built in which is successful retry logic. One thing which I want to mention is the web service security which is part of the Soap protocol. The first thing is authentication. So how do we make sure that our client is able to reach the server? We can have user credentials, we can have X 90 509 certificate. We can have samples to make sure the client is who they say they are. The second thing is confidentiality, which means that if they want to send a message to see, we should not be able to view that message. So the message has to be encrypted. The third thing part of the security is integrity, which means that the data which was sent from A to it is the same message which is going there. So you can implement it by using hashing or signature. This will ensure that the message which is received at is the same message that was sent by Amity is not manipulated. The fourth part is non repudiation, which actually means that if replay attack happens, it should stop it’s for example, if I keep sending the same message again and again card does it, the security should be able to figure it out.

3. API-led Connectivity

Let's look at the pre 2015 error project. The first thing will be a human solution. It will be a monolithic solution. It will generally be web first. So you will have webcam and calling certain processes. Within that, there'll be a system of record, let’s say SAP or database which will be used. And this project will take at least one year to finish. After six months, we'll realize that you actually need to connect mobile. So there will be an extension of this project. Probably take another six months to complete. There may be new dependencies, but a lot of work will be done to rewrite the same project. Again in terms of P four and P five. So, what's the better solution? Let’s take a look at. Now, a better approach is API Led connectivity. It is a methodological way to connect data to applications through reusable and purposeful APIs. Let's look at what I need. So, we have segregated layers in terms of system, process and experience. We unlock data from the system, compose data into a process and then deliver an experience. By this, we ensure that code reuse is one of the major things API Led for organization empowerment. The system APIs can be unlocked by the central It process. APIs are composed and made reusable by line of business. It the experience. APIs are discovered and consumed by third party developers. Now, the center for enablement that team can facilitate this approach. And a good KPI to measure that is to find out what is the asset consumption and reuse you.

Hide

Design APIs

1. Design APIs

Some of the examples. As you can see, I have mentioned some URLs for planets and the sun. So in the top bar you will see that the planet API has been called. And I can see two planets which are being returned in this API and you can see more information on them. There’s also a Sun API which is giving me the diameter of the sun. How many moons does it have? Let's look at some Restful request methods and how do we use them. There’s a Get method which will tell you about the current state of our resource. For example, we saw that if you want to get single planet's information, we'll use a Get post is something when you want to create a new resource. Let’s say a new planet was discovered in our solar system and you want to add it, we will use the post method. Delete would be to remove the resource. Now that we know Pluto is not a planet anymore, we could use the Delete method in the Restful source, but will be used to replace the resource. Let’s say an asteroid was turned as a planet and now we want to replace it with a real value. We can use a put method. Patch is when you want to partially update the resource. Let’s say in 2030 there are more people in Marchland we want to change how many people or the human count in Mars we will use the patch method. You already saw the JSON response, but what is it? JSON is JavaScript object notation. It’s like weight, it's data interchange format. It is human readable. It supports collections and maps. What you see in the top bar is adjacent and the similar. If you want to convert it into an XML it's at the bottom you will see subtle differences in which we are not wasting a lot of the same term like menu item again and again for each item in the row. So there are many other reasons why JSON is more human friendly and why people like it so much. Let’s talk about Ramen. Ramen is restful API marketing language. It manages the API lifecycle from designing to sharing. It is human friendly and machine readable. So that's a plus. It’s reusable and concise and you can add your resources like Get put post into it. You can create collections and trades. You see a very basic example of Ramen, which is using version 1.0 from the eBook Mobile API of version Bone some of the end points of Ramadan is mentioned here. If you want to have books on planets, on aliens, on alien author, there are a certain way you will have to indented inside of a Ramble. As you see on the left hand side that there are books and then books title and then you have authors and it has a Get method. So once you practice with Ramble, you will understand this clearly. When you are designing your APIs. It is good to know these Http error codes. I can give you some time, or you can pause this video to see some error codes here. Some of the common Http error codes is 200, which is the perfect one. It says okay, and you might have encountered500, which is the internal server error. Let’s look at some database terms, because thesis being used a lot in Paisa database is a collection of related data organized in an Rdvms. DDLS are used when you want to create databases or tables. DMs are used when you want to insert or update data in those tables. And DCLs are used when you want to-do access control on certain users groups. Data redundancy is a way of storing that same data in multiple locations for fault tolerance and faster. It cheaper. Normalization is the total opposite of data retailers.

2. JDI: Create API with RAML

So I filled up my information for signing up on Any point of platform, I need to agree to the terms and click on Accept and Create account. This is the landing page of the Any point platform, which is the access management. You can see my organization name here. Let's click on this hamburger menu which will lead us to the Design Center. So I just clicked on Design Center. This is the place where we'll be working to create new applications and create API specs. As you can see, I don't have any projects. So let's create one by clicking on this Create button. Now, you have two options. You can either create a new mule application or you can create an API spec’s let's click on this grey button to create a new API specification. Since this is a new project, I’m going to call this planet Apian I'm going to choose start with API Designer because want to create a new route for this. This is the API designer. This is a place where you can create your specifications, which you can use to develop, deploy and manage your APIs. We also see the syntactical suggestions which are there, and this will help us to create more services. So let's get started. So this is the API designer. What you see in front of you is caramel which is opened up of version 10. The title is Planning API. This is the same name what we gave the project, US. And you can use this to create a spec which is basically your endpoint, which will be there. You also have mocking service, right, built into this. And on the right, you also see a good Union terms of what all API's you will create. So what I want to do with this projects I want to create two endpoints right now. First one is called Planets. This will give me a list of all the planets which are available. So I'm going to have a get method inside of this, which is initiative method. The second endpoint which I wanted to make is, let’s say if I want to get more information about a particular planet, I can pass in and of the planet like so the colon, and then invent another get method inside of this. So what will happen is, let's say if I pass in value like Planet One, I will get more information about the first planet or the planet which has ID one. On the right, you can see there are two endpoints created the same thing which I did. For now, that you've created your API spec, let’s look at creating a new mocking service. And hitting that endpoint, I'm going to click on the Toggle button. What it does is creates a base Uri inside the Rammer and the same link you can see on the right hand side for you to use and hit it with any thin client like Postmark. So let me open up Postman and I'm going to paste this URL and I'm going to do a Get call to this and click on the Send button. What I just did is try to go on this URL and got some information. In this case we got a 404 meaning that there was nothing here and that's very strange, right? Because we tried to hit the mocking service as nothing returned. But there is something which we did wrong, which is that we didn't provide the complete URL here we need to add in planets and then again send. In this case we did get a 200which means something was there and it was successful but we did not get any values. Same thing if we try to hit the other endpoint, let’s say if I put in a slash two, which is the ID, and I'm really going to get a 200, okay? As the status and nothing in the body is the response. So let's look at how can we create some examples for this. The first thing you want to do is stop smoking service and let's add a bunch of planets as examples which we will get in the response. So in the Get method I'm going to add a new response. So the way to do it is add responses. Then I need to put in the status code of the response. So I'm going to choose 200.The next thing I want is a body. I also need to specify the type of the response which has been sent which will be adjacent. So I have to choose application son. And lastly I need to provide this keyword example. Come back heretic already have a copied value for the response which want to send and I'm going to paste that here and I'm going to click this toggle button again. If everything went well, I'm going to hit this endpoint again. Coming back to Postman, paste this value and remember Indeed to hit the planet endpoint now when I press Save or Send I'm going to get a a 200. But this time you see, I also have some JSON, which has information about the planets, and this is what we wanted.

3. Publish API to Anypoint Exchange

So I added some more planets and examples in this. And you can take a look at this Ramen. You will be getting it as part of this course. And what I want to do this time is have have a Mocking service. And you can look at this URL to get more information. But what I want to do now is publish to Exchange. There’s this blue button. Let’s click on that. It’s going to ask me a bunch of questions about what I want about this Exchange. So what I'm going to does just change this asset version. This is our first version which we are going to publish. By clicking on that, we have sent information that we publish this API spec to Exchange. Let’s look at how it so this is how it would look like. So it has successfully published it to Exchange. Now let's look at how it looks like. In exchange with this, you are able to have an API without doing any coding, doing any implementations. Have a spec ready for your stakeholders to see how it looks like. Here you see a bunch of things. You have the information of sharing it, downloading it. You can use this API inside an existing application which you are developing. There’s also a Mocking service associated. So you can see there's an instance and you can look at it how it is in the API designer. You can add a new version. You see all of these things. Because we are the people who created this together. So we are the owners of this Apies can click on Summary to see the exact URL which is existing for this API. You see only one URL which is the Mocking service. As you create your implementations and host it on cloud, up, on premise, you will see more versions of these. It also gives you a summary of the endpoints. You can click on this API instance which will give you more information about the URL, the visibility, and also create new instances for you. You have completed it, an API spec and you are ready to share with your stakeholders.

Hide

Any point Platform

1. Anypoint Platform and Anypoint Exchange

Let's first talk about any point exchange. Now, what you see is any point exchange. I’m on this URL, you can see all the assets which are provided by MuleSoft. You can see an SAP connector, salesforce connector, all your assets and all the content that will be available here. Let's say you are part of an organization and you try to log in. Now, what you're going to see is the private version of the exchange. I mean, you can have your APIs to be publicly available, but all the assets which you seeing your organization will be found here. The planet's API which we created in the last US lesson is also available here.

2. Assets

Let's look at different assets content types. The first one is connectors. Connectors are facilitators for any third party API to be integrated with new APIs. Then comes standard templates which are best practices or common use cases. Then is example which is a demo of a solution for an enterprise. Next is APIs. Could be Rest Soap or http based Then it's API spec fragments which are used in RAML. Last but not the least is Custom or any miscellaneous workers. The next slide talks about what do you need to create those assets. So connectors, templates and examples can be used using Maven or using any point studio, Rest, API, Rammer and APS fragments can be manually created or created using differently line center for Http or Soap APIs. You can create them manually.

3. Sem Ver

Semantic. Versioning 20 is an important way to version your APIs. How do you get to know that you need to bump up a version? When you make a major version change, it means that your API changes are incompatible with the previous change. A minor version change is when you add functionality to the API but it is backward compatible. A patch version change is when your changes are backward compatible and mostly used for bug fixes.

4. API Manager and Anypoint MQ

Let's talk about two of the important products within any point platform. The first one is API manager. As the name suggests, it manages your APIs from design to distribution. It is tightly integrated. It with Design Center Exchange Studio. You can import your APIs using Zip or Ramble. You can configure policies slaters you can even look at analytics, which is given by API gateway, and it helps you in setting up your environments. The second one is any point Milt’s an enterprise wide multitenant cloud messaging service. It’s mostly sync messaging, and it also has a Rest API for non-new labs. It has availability zone configuration. It is encrypted by nature. The maximum size of the message could be up to ten max. The time to live for these messages is of max two weeks. When you configure non fee for messages. Your limit or number of queue messages which can be stored inside of this is 120,000, whereas for fee before it is only $10.

Hide