Are you using the right API technology for your microservices ?

Are you able to build the required features using your choice of Api specification seamlessly?

As a developer how do you measure the performance of your Api code to analyze if you had made the right choice for the right use case?

APIs are at the heart of the modern software development in building on-premise , cloud based and cloud native applications .

In this era of modernization and digitization , web based services and APIs are the main tools for communication.

When choosing a technology to build the APIs , organizations and teams mostly rely on their previous experience and/or pick the ones that are widely used . And more often than not they do not provide a precise solution for all business needs. Any third party vendor solutions or other workarounds adopted impact the performance of the API in a negative way.

A production-ready Api is more important than a feature-complete Api ; to achieve that you ought to choose the right technology. By default many of us use different versions of the REST based Web Api framework with ASP .NET or ASP .NET Core to build all our microservices. There is no doubt that we always achieved the desired functionality , but many times with a bit of a compromise on the performance and flexibility.

However , there are other options that are worthy of consideration.

In fact ,they prove to be better than the REST based Web Apis if used for the right scenarios.

GraphQL and gRPC are two of the modern API specifications introduced and open sourced by Facebook and Google that are slowly becoming the alternatives that can be used seamlessly in .NET applications.

In this course we are going to learn in detail about the .NET implementations of GraphQL and gRPC along with the REST Api Architectural Style .

We have dedicated sections where we discuss the core concepts of these technologies and understand what makes them unique from each other . We will build a real world microservice in .NET 5 for each and test all the features with proper examples using .NET 5 Client (s) .

Not just that , In the fourth section we will also learn about the powerful .NET library BenchmarkDotNet which is very efficient in benchmarking .NET Code.

The Main Objective of this course is to benchmark the three microservices that we created in the first three sections by conducting a variety of experiments that will help us determine the ideal scenarios where each of the API technologies excel. BenchmarkDotNet is the best tool for that task.

By the end of this course you will not only be able to begin to use the API technologies by yourself but also be able to decide where you can use them optimally to improve the Api Developer Experience leading to improved Organizational Experience and Customer Experience. This course will give you the required jump start to widen your tech skillset.

This is the only course that teaches you 3 API specifications together . You will gain first hand experience on how to create the same features across the three APIs and compare them to generate the required insights.

In one course you will get the deal of five courses !!

Majority of the videos are hands-on code along lectures.

What you need is C# experience .

If you are already an API developer who have already used the Web Api framework , its great . If not , it is still okay as we are going to create each API step by step starting from choosing the project template.

Go through the Intro and the Course Content Videos to get an idea of what we are going to cover.

Looking forward to see you in the course .

Happy Learning !!

SeedACloud Team