Polymorphic messaging is a powerful concept that can assist with message contract migration in production environments as well as build message inheritance hierarchies for groups of related use cases. One often overlooked use for polymorphic messaging is to partition data along boundary lines between "internal" events and "external" events.
In Part 3, we pulled back the curtain on Visual Studio Publish to gain insight into what it was doing in order to deploy our NServiceBus endpoint to Azure. Using that newfound knowledge, we'll be "graduating" from right-click/Publish to Azure DevOps.
One of the many features of NServiceBus is the ability to encrypt specific properties/fields in your messages. NServiceBus property encryption ensures sensitive data in messages are encrypted at-rest as well as obscured from system administrators when they end up in your error queue. Property encryption also has the benefits of leaving non-sensitive data in the message available for debugging purposes.
In Part 2, we used Visual Studio's Publish feature to deploy our NServiceBus endpoint to an Azure App Service, and after only one manual change in the Azure Portal, saw our endpoint successfully running by viewing the app service logs. In this post, we'll be pulling back the curtain on Visual Studio Publish to examine what's happening in your local solution and in Azure.
Having a local development environment that emulates AWS cloud services can be an extremely handy tool when developing NServiceBus endpoints that use AWS services. LocalStack is that tool and in this article I will describe what LocalStack is, how it is useful and how to get started with an example project.
In the last post we coded an NServiceBus endpoint running in a hosted service in the .NET Core generic host. Now that we have an endpoint, how do we deploy it to an Azure App Service? Like all things in life, when in doubt, right-click! More specifically, right-click, Publish.
As the cloud slowly becomes the norm rather than the exception, frameworks built with .NET have to find a way to run in new cloud-based hosting models. This post is the first in a series on how to code, build, deploy and run an NServiceBus endpoint in Azure App Services.
Recently, we have had several clients trying to solve the age-old problem of file processing, and in both cases a quick reference to this old presentation from NSBCon 2014 seemed to help them in their implementation. If you are trying to process large amounts of data from flat files into your system(s), this presentation is a great showcase of our own approaches, lessons learned, and anti-patterns that may help you!
This video starts with a lightning talk by Gomti Mehta as an introduction to Domain Driven Design. The main talk, given by Indu Alagarsamy of Particular Software, delves deeper into DDD and Bounded Contexts from the perspective of an event-driven architecture.