Cesar de la Torre [Microsoft] - BLOG

Principal Program Manager at the .NET product Group (Microsoft Corp in Redmond, Seattle). Focus on Machine Learning .NET (ML.NET), .NET Core, Microservices based architecture, Docker Containers, Azure services. Check out http://dot.net/Architecture and https://github.com/dotnet/machinelearning-samples

How to optimize and run ML.NET models on scalable ASP.NET Core WebAPIs or web apps

Context
This article explains how to optimize your code when running an ML.NET model on an ASP.NET Core WebAPI service. The code would be very similar when running it on an ASP.NET Core MVC or Razor web app, too.
Eventually, this kind of optimized code might be provided as an .NET Core Integration Package comparable to integration packages targeting Entity Framework,

Designing and implementing API Gateways with Ocelot in .NET Core containers and microservices architectures

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.

Microsoft eBook gratuito en Español: “Microservicios .NET – Arquitectura para aplicaciones .NET contenerizadas” – Docker, .NET Core, Kubernetes, Service Fabric, Azure.

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,

Implementing background tasks in .NET Core 2.x webapps or microservices with IHostedService and the BackgroundService class

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.

Modernize, lift and shift, existing .NET apps with Windows Containers and Azure

************************** NOTE ************************
This blog post is a replica of the same blog post I just published at the official Microsoft .NET Blog, here:
https://blogs.msdn.microsoft.com/dotnet/2017/11/01/modernize-existing-net-apps-with-windows-containers-and-azure/
********************************************************
As part of the series of posts announced at this initial blog post (.NET Application Architecture Guidance) that explores each of the architecture areas currently covered by our team, 

Best-in-class Microservices and Domain-Driven Design conference and workshops in the U.S.!! Explore DDD 2017 (Denver, September 19-22, 2017)

Explore DDD 2017 is a brand-new Domain-Driven Design (DDD)-centric conference, September 19-22 2017 at the Grand Hyatt hotel, in downtown Denver, Colorado, USA.

I’m not directly related to this conference, but I wanted to provide some support/awareness because this type of quality events is fundamental for the development and software architecture community.

Using Domain Events within a .NET Core Microservice

This blog post is related to the previous blog post named “Domain Events vs. Integration Events in Domain-Driven Design and microservices architectures” : https://blogs.msdn.microsoft.com/cesardelatorre/2017/02/07/domain-events-vs-integration-events-in-domain-driven-design-and-microservices-architectures/
Since I’m writing content related to “Microservices architecture, Docker containers and .NET Core” (draft available here, at GitHub),

Uncategorized

How to optimize and run ML.NET models on scalable ASP.NET Core WebAPIs or web apps

Context
This article explains how to optimize your code when running an ML.NET model on an ASP.NET Core WebAPI service. The code would be very similar when running it on an ASP.NET Core MVC or Razor web app, too.
Eventually, this kind of optimized code might be provided as an .NET Core Integration Package comparable to integration packages targeting Entity Framework,

Designing and implementing API Gateways with Ocelot in .NET Core containers and microservices architectures

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.

Microsoft eBook gratuito en Español: “Microservicios .NET – Arquitectura para aplicaciones .NET contenerizadas” – Docker, .NET Core, Kubernetes, Service Fabric, Azure.

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,

Implementing background tasks in .NET Core 2.x webapps or microservices with IHostedService and the BackgroundService class

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.

Modernize, lift and shift, existing .NET apps with Windows Containers and Azure

************************** NOTE ************************
This blog post is a replica of the same blog post I just published at the official Microsoft .NET Blog, here:
https://blogs.msdn.microsoft.com/dotnet/2017/11/01/modernize-existing-net-apps-with-windows-containers-and-azure/
********************************************************
As part of the series of posts announced at this initial blog post (.NET Application Architecture Guidance) that explores each of the architecture areas currently covered by our team, 

Best-in-class Microservices and Domain-Driven Design conference and workshops in the U.S.!! Explore DDD 2017 (Denver, September 19-22, 2017)

Explore DDD 2017 is a brand-new Domain-Driven Design (DDD)-centric conference, September 19-22 2017 at the Grand Hyatt hotel, in downtown Denver, Colorado, USA.

I’m not directly related to this conference, but I wanted to provide some support/awareness because this type of quality events is fundamental for the development and software architecture community.

Free eBook/Guide on ‘.NET Microservices – Architecture for Containerized .NET Applications’

The microservices architecture is emerging as an important approach for distributed mission-critical applications. In a microservice-based architecture, the application is built on a collection of services that can be developed, tested, deployed, and versioned independently. In addition, enterprises are increasingly realizing cost savings,

Using Resilient Entity Framework Core Sql Connections and Transactions: Retries with Exponential Backoff

There are many possible approaches to implement retries logic with exponential backoff also depending on the context/protocol, etc. (Database connections, HTTP requests, etc.)
Retries with exponential backoff is a technique that assumes failure by nature and attempts to retry the operation,

Using Domain Events within a .NET Core Microservice

This blog post is related to the previous blog post named “Domain Events vs. Integration Events in Domain-Driven Design and microservices architectures” : https://blogs.msdn.microsoft.com/cesardelatorre/2017/02/07/domain-events-vs-integration-events-in-domain-driven-design-and-microservices-architectures/
Since I’m writing content related to “Microservices architecture, Docker containers and .NET Core” (draft available here, at GitHub),

Domain Events vs. Integration Events in Domain-Driven Design and microservices architectures

This blog post is about comparing several approaches of Domain Events vs. Integration Events patterns already published by the community. I might evolve this post depending on feedback and some implementations we’ll be doing in the short/medium term. So, feel free to discuss about it with comments at the end of this post.