Microservices: Passing Parameters
Most of the time your microservice API methods will take parameters. This post will review how we send parameters with a web request and how we interpret those parameters correctly on the server. Passing Parameters in a Web Request Let's consider how information might be communicated in a web request. First, what are the components of a web request? We have: The request verb and URL Request headers (including cookies) The body ...
Microservices: Type Discovery and Instancing
Let's suppose that a web client has the URL of your microservice endpoint. When the client makes a web request to that endpoint, how does the correct code get called on the web server? Our microservice consists of code running on a web server organized into classes in an object-oriented language, and each microservice endpoint corresponds to a unique method in one of these classes. In my discussion of endpoint naming I used this ...
Serving up a Microservice API: naming
In my last post, I described a microservice as a set of web API endpoints. When implementing a microservice framework then, our most fundamental task is to provide those endpoints. There are a number of things to consider, and one of the first steps is to decide what and how the endpoints are called. What is an API endpoint again? An API endpoint is just a URL that can be called from a web client such as a browser application. Unlike a ...
Microservices: What and Why
We've spent the last year at Home Depot building a C# microservices platform with the new ASP.NET Core. This has been an exciting development and we're really happy with what we've achieved so far. Over the coming months, we'll be open-sourcing our framework and sharing our experience. I'm going to write a series of posts that cover all of the gory details, but first I'd like to start with the basics of what a microservice is and why they ...
Windows Store apps: StreamSocket connection to localhost
The problem: running unit tests on a Windows Store app that connects to a port on localhost results in the error "A connection attempted failed because the connection party did not properly respond after a period of time ...". Connecting to a loopback address (127.0.0.1 or localhost) is not supported in a Windows Store application. Period. However, connecting to localhost while debugging an application in Visual Studio IS supported. ...