Over the past couple of years, we’ve had more and more customers start building applications that run on Microsoft Azure.
While doing these projects we noticed that there were components we had to implement over and over to build a boilerplate for our applications.
Of course this meant we were doing the same thing over and over again. So we decided to do something about.
We are happy to announce Arcus, our open-source family of libraries and components that makes it easier to build applications for Microsoft Azure.
Our goal with Arcus is to fill the gaps that we consistently experience, so we don’t have to reinvent the wheel each project. If there is already a component or library that does the job, we prefer to support that community.
Today, I will show you what we have done up until today and where we are going.
Event Grid
Our first component is Arcus Event Grid which provides capabilities to more easily integrate with Azure Event Grid:
- Provides capability to handle Event Grid validation handshake
- Provides capability to receive events
- Provides capability to push typed or raw events
- Provides infrastructure for integration testing (More in this blog post)
- Provides support for using official Azure events
(Deprecated in favor of official Azure schemas, see #46)
Let’s have a quick look at how easily we can push events.
Pushing events
Getting started by pulling in our NuGet package
PM> Install-Package Arcus.EventGrid.Publishing
First, we will create our own NewCarRegistered event:
For the sake of this post the NewCarRegistered class is not included but you can have a look on GitHub and our docs how to do achieve this.
Next we will create an Event Grid Publisher and publish events to the topic.
In this example, we only push one event, but we also support sending batches via PublishMany.
If you want to be more flexible in the event payload you can also publish raw events:
Event Grid Proxy
Integrating with Azure Event Grid is simple and, hopefully, Arcus Event Grid makes it even easier for you to do so!
However, in some cases, this is still overkill because we need to write custom code to push schemas while that code still needs to run somewhere.
It would be easier if we could just push events via HTTP, without having to worry what the endpoint is and how to authenticate.
This is exactly what Arcus Event Grid Proxy does. It is a simple Docker container which accepts HTTP requests and will forward it to the configured Azure Event Grid topic.
By using a Docker container, you can basically deploy it wherever you want – be it on Service Fabric Mesh, as a side-car in Kubernetes, on-premises or simply on your laptop for local testing.
Using Arcus Event Grid Proxy
Just pull in the container and start pushing events to it:
Sending events is just as simple as doing an HTTP POST to it with the event payload, or provide more context about the event.
The beauty is that not only does it allow you to easily get started, it also allows you to send events to Azure Event Grid that don’t yet support it, without having to implement and run your own code on Azure to achieve this.
Use the correct tag for the job
Different use-cases require different image tags, that’s why we provide three flavors of them.
We strongly recommend reading more about our tagging strategy and only use arcusazure/azure-event-grid-proxy:latest for POCs.
Security
Security is one of the most important aspect when building applications, this is no different on Microsoft Azure!
With Arcus Security we’ve started with a nice and simple secret provider that allows you to get secrets:
You can easily get started with Azure Key Vault:
PM > Install-Package Arcus.Security.Secrets.AzureKeyVault
As of today we only support Azure Key Vault, but we might add more providers later on.
Authentication
Our aim was to make it super easy and provide seamless authentication by doing the Azure AD integration for you.
We have a couple of authentication schemes that are currently supported, but more will follow such as certificate authentication.
Caching Secrets
In order to avoid hitting the service limitations of Azure Key Vault we also allow you to cache secrets:
This will be stored in an in-memory cache so secrets are not leaked and it is configurable to fit your needs.
What’s next?
While we already have some components covered, this is just the beginning.
We are planning to build upon our existing components but also expand to other areas:
- We want to make certificate authentication easier (Building upon on our security component)
- Provide a simple way to enforce shared access key authentication (Building upon on our security component)
- Provide more authentication mechanisms for Azure Key Vault
- …
Want to learn more? You can get started here:
| AREA | DESCRIPTION | LINKS |
|---|---|---|
| General | General request or suggestions for new areas | File an Issue |
| Event Grid | Requests & suggestions for Azure Event Grid integration | Features – File an Issue |
| Event Grid Proxy | Requests & suggestions for Azure Event Grid Docker container | Features – File an Issue |
| Security | Requests & suggestions for security integration(s) | Features – File an Issue |
We are open to suggestions and are happy to accept pull requests!
Thanks for reading,
Tom.
Subscribe to our RSS feed