My Profile Photo

Miroslav Janeski

Miroslav Janeski - EngD | Technical Director | Process Mining Expert | Microsoft MVP (Azure - Application as a Service & .NET)

  1. How to Use the Azure Durable Task Scheduler Emulator in .NET Aspire

    Azure Durable Task Scheduler (DTS) is Microsoft’s managed orchestration backend for Durable Functions — a fully integrated alternative to the classic Azure Storage-based state store. It brings better performance, a built-in dashboard, and a cleaner operational model. …

    • on dotnet, aspire, azure, durable-functions, durable-task-scheduler, cloud-native, csharp, microservices, containers, devops, iot, azure-container-apps

  2. What Makes Azure App Service Cloud-Native — and What Still Doesn't

    TL;DR …

    • on azure, azure-app-service, cloud-native, paas, containers, microservices, dotnet, devops, kubernetes, azure-container-apps

  3. Microsoft Azure — Leader in the 2025 Gartner Magic Quadrant for Cloud-Native Application Platforms

    Microsoft has been named a Leader in the 2025 Gartner® Magic Quadrant™ for Cloud-Native Application Platforms — for the second year in a row! Even more impressive, Microsoft is positioned furthest to the right for Completeness of Vision. …

    • on azure, cloud-native, gartner, microsoft, dotnet, paas, azure-container-apps, azure-app-service, ai, serverless, microsoft-mvp

  4. Azure Container Apps vs AKS vs Azure Functions: The Best Cloud-Native Choice for .NET Developers

    The most correct answer to the question “Is Azure Container Apps the best cloud-native alternative for .NET developers?” is: It depends! However, that answer doesn’t give any value. So let me elaborate further on my reasoning. …

    • on azure-container-apps, aks, azure-functions, cloud-native, dotnet, dapr, aspire, azd, kubernetes, microservices, serverless, azure, csharp, devops, containers

  5. From Dev to Deployment: Getting .NET Aspire to Azure with Azure Developer CLI (azd)

    .NET Aspire simplifies local development and brings the architecture closer to the development team. These are the main takeaways from my last article. However, we cannot talk about cloud-native applications if we only focus on local development. The main idea behind cloud-native applications is the new perspective on efficient development and moving to production. The main task of the tools in the cloud-native landscape is to make the whole process much easier, simple, and generally efficient. …

    • on dotnet, aspire, azure, azure-container-apps, azd, cloud-native, devops, containers, csharp, bicep, deployment, microservices

  6. Streamlining IoT Development: A Minimalist Approach with .NET Aspire, MQTT, and TimescaleDB

    Local development is a serious challenge when developing distributed systems, especially IoT solutions. The development team often requires end-to-end local development to complete the job. For example, imagine you have to tweak the real-time update on your charts in the web app — you either need an IoT device simulator or plug into the development environment. In both cases, you need the process automated. Otherwise, it will become cumbersome and too expensive. …

    • on dotnet, aspire, iot, mqtt, azure, signalr, timescaledb, cloud-native, microservices, csharp, containers, devops

  7. Light and Fast: Building Cloud-Native Microservices with Azure Functions and Dapr Extension

    In today’s microservices-driven world, managing communication between services can become complex and cumbersome. Azure Functions, Microsoft’s serverless computing service, offers a powerful way to run event-driven code without worrying about the underlying infrastructure. The serverless concept is not new, and I have already shared a couple of posts regarding its benefits. The inspiration for this post comes from a recent feature released by the Azure Functions team: the Dapr Extension for Azure Functions. …

    • on azure-functions, dapr, microservices, cloud-native, azure, azure-container-apps, service-bus, cosmosdb, dotnet, csharp, distributed-systems, serverless, devops

  8. Reducing Azure Functions Cold Starts: Tips from the Azure Functions Team

    The Azure Functions team has shared key improvements to minimize cold start times for Azure Functions. These updates promise enhanced performance and a better user experience. …

    • on azure-functions, cold-starts, serverless, microservices, cloud-native, azure, performance, dotnet, flex-consumption, devops

  9. When to Go Serverless with Azure Functions: A Rule of Thumb for Enterprise Architecture

    If you are wondering when you should go for serverless, especially in the context of an enterprise solution, I have a rule of thumb for you. …

    • on azure-functions, serverless, cloud-native, azure, microservices, architecture, dotnet, scalability, devops

  10. Azure Functions Flex Consumption: Solving the Cold Start Problem Without Losing Pay-Per-Use

    I’ve been using Azure Functions since version 1.x. I love the serverless model. It represents the core of being cloud-native. It enables the engineers to focus on the business logic while spending less time on the infrastructure and some of the cross-cutting concerns. …

    • on azure-functions, serverless, cloud-native, azure, flex-consumption, cold-starts, microservices, dotnet, scalability, build2024, devops