We’re currently evolving the .NET microservices guidance and eShopOnContainers reference application. One of the most important topics is about the API Gateway pattern, why it is interesting for many microservice-based applications but also, how you can implement it in a .NET Core based microservice application with a deployment based on Docker containers.
Las arquitecturas basadas en Microservicios están emergiendo actualmente como opciones apropiadas para aplicaciones distribuidas de misión crítica.
En una arquitectura basada en microservicios, la aplicación se construye basada en una colección de servicios que deben ser desarrollados, probados, versionados y desplegados en producción,
Background tasks and scheduled jobs are something you might need to implement, eventually, in a microservice based application or in any kind of application. The difference when using a microservices architecture is that you can implement a single microservice process/container for hosting these background tasks so you can scale it down/up as you need or you can even make sure that it runs a single instance of that microservice process/container.
Even when these official images are still evolving, I think that a summary about the multiple Microsoft Docker images for .NET available at Docker Hub would be a “nice to have” thing.
This blog post is related to my previous blog post on “Docker containers – Should I use .NET Core or .NET Framework?”,
The short answer is: “For Docker containers, use .NET Core whenever is possible”. But, below is a summary decision table depending on your architecture or application type and the server operating system you are targeting for your Docker containers.
Take into account that if you are targeting Linux containers you will need Linux based Docker hosts (VMs or Servers) and in a similar way,
Last week (Sept. 19-22 2016) I delivered a similar event in Buenos Aires and in Santiago the Chile, afterwards. Here I post the agenda I delivered, a few pictures about it plus the decks I used about it.
Morning Event – Developing microservices in the Cloud with .NET,
In .NET Core 1.0 apps (either ASP.NET Core apps or Console apps, as of today) there are new possibilities like being able to run your app (like an ASP.NET Core app) on top of the .NET Core Platform or on top of the traditional .NET Framework 4.5.x which is critical for many enterprise apps that still might not have all the libraries/components compiled for .NET Core available (custom or third party).
I’m writing this blog post about “.NET end-to-end” now that we just released the .NET Core Platform 1.0 RTM, so it’s clear “who is who” and “when to use what”. It’s a long post but I think it’s good to have available a single post about .NET end-to-end.
(UPDATE – Nov.2016) – Note that .NET 5 and ASP.NET Core 5 were temporal brandings while .NET Core was in beta. Its final branding was .NET Core 1.0 and ASP.NET Core 1.0 when released in June 2016, due to the big shift or “reset/modernization”