Skip to main content

Posts

Showing posts with the label HTTP

Microservices: How to choose right API style that fits to your Solution Requirements gRPC over Restful

Hello Welcome to this post!   An effective API design is vital in a Microservices architecture because all data exchange between services happens either through messages or API calls. REST style is probably the most known as it has become common among the Web API. But lately, the gRPC framework is becoming quite popular to build high performance systems. So, you might get these questions when involving in designing an API architecture. In this post , you would be able to find answers and to understand the capabilities of gRPC framework, features of Protobuf and HTTP/2 protocol and finally overview of common use cases of gRPC over REST API. so, let's keep reading further for technical insights. REST: a brief overview Before we start looking into details of the gRPC framework, let’s take a brief overview of RESTful services first. The standard REST methods built on HTTP 1.x. with well-defined status codes help in identifying cause of problems. Generated contracts, m...

WCF or WebAPI - When to use the Web API over WCF considering HTTP Methods Advantageous

In this post, we will learn what is the difference between WCF and Web API? and, when to use the Web API  or the WCF considering HTTP methods advantageous.Let's explore the features from MSDN theories now and to summarize the final decision. WCF and HTTP model? WCF is the framework to build services that are flexible with regard to transport, encoding and various protocols. Building services and planning to support multiple protocols or support other than HTTP protocol (tcp, name pipes etc.) then WCF should be a best choice. ========================================================= Advertisement: Choosing .NET Core Worker Services OR Windows Services? ========================================================= If we happen to want to expose WCF service over HTTP protocol then there are two high level choices: Soap over HTTP and Web HTTP. Soap over HTTP is simply a different binding/endpoint choice. Web HTTP model changes the dispatching to happen based on URI templates an...