Learn how nanoservices differ from microservices and how to build them with ASP.NET and Azure Functions.
Read more…
Brought to you by one of our Guest Author member crew! Joydip Kanjilal
How did you like this post? Please share any comments or feedback with us on this thread
I have to disagree on the presented solution following the architecture principles you elaborated. In fact each of your so called nanoservices is an azure function tightly couple with the business service class (they are just proxies to the service class method). They act just like an access channel to the business service class.
The intent of this article is providing the reader a hands-on guide on implementing Nanoservices in ASP.NET Core. In the article it is clearly stated: “The business logic component of our microservice is responsible for providing its core functionalities. This being a minimal implementation of a microservices-based application together with its nanoservices, you wouldn’t actually have any business logic as such in this component. In our case, it will act as a passthrough between the CartManager class we will implement in a later section and the repository.”
How would you secure this Nanoservice API in Azure Functions? I noticed in Auth0 Quickstarts that ASP.NET Core is listed which uses a middleware to validate the JWT. Azure Functions does not support this middleware configuration, but Azure Functions is not listed in the Quickstarts list. A followup question would be, does this mean that Azure Functions is not an officially supported scenario for Auth0?