Azure

Posts in this series: Evaluating the Landscape A Generic Host Azure WebJobs Azure Container Instances In the last post, we looked at Azure WebJobs as a means of deploying messaging endpoints. And while that may work for smaller loads and simpler systems, as the number of message endpoints grows, dealing with a "sidecar" in a WebJob starts to become untenable. Once we graduate from WebJobs, what's next? What can balance [Read More]

Posts in this series: Evaluating the Landscape A Generic Host Azure WebJobs Azure Container Instances In the last post, I looked at creating a generic host endpoint that many of the deployed versions in Azure can share. By using a hosted service, we can then host NServiceBus in just about anything that can work with the .NET Core generic host. The differences then come to hosting and scaling models. First [Read More]

Posts in this series: Evaluating the Landscape A Generic Host Azure WebJobs Azure Container Instances In the last post, we looked at the many ways we can consume messages in Azure as a message endpoint. Unfortunately, there's not an easy answer. We don't have a simple, PaaS solution to a background service. We basically have some very bare serverless options, some shimmed options, and IaaS options through containers. Regardless of [Read More]

Posts in this series: Evaluating the Landscape A Generic Host Azure WebJobs Azure Container Instances When looking at moving traditional on-prem solutions to the cloud, I try as much as possible to avoid any kind of lift-and-shift strategy and instead leverage as many platform-as-a-service (PaaS) offerings as possible. Since our systems mainly consist of web applications backed by some sort of database, it's often a fairly straightforward transition. Web applications [Read More]