Skip to main content

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB!

So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Configuration Provider and modified it to support Azure Cosmos DB. Enter Narad - an Azure Cosmos DB Configuration Provider for .NET Core.

To use Narad, first create a Cosmos DB database and upload your configuration data as JSON file in one of the collection. There are excellent instructions available on MSDN docs on how to do this. Next clone or download it from GitHub repository and add the reference to "Narad.Extensions.Configuration.CosmosDBCore". Narad is now available as a Nuget package. Search for "Narad.Extensions.Configuration.CosmosDBCore" or follow this link - https://www.nuget.org/packages/Narad.Extensions.Configuration.CosmosDBCore/.Also in your appsettings.json, you will have to provide the following details:

The database and collection name can be whatever you want. Next in Program.cs, add the AddCosmosDB() method. You are done! Optionally you can also bind your configuration POCO class to the configuration values retrieved from Cosmos DB as shown in the Startup.cs.


You can find the complete source code as well as sample client on GitHub - https://github.com/mayankthebest/Narad

Comments

  1. Its very informative blog and useful article thank you for sharing with us , keep posting learn
    more about .NET Online Course Hyderabad

    ReplyDelete

Post a Comment

As far as possible, please refrain from posting Anonymous comments. I would really love to know who is interested in my blog! Also check out the FAQs section for the comment policy followed on this site.

Popular posts from this blog

Pi Hole - Ad blocking (Turbocharged!)

The entire internet is now made up of ads. To easily navigate it and find the information you are looking for, most people use ad blocking software. It improves page loading times and also uses less data (sometimes by up to 10 times!)
Google Chrome is the de facto browser of choice for most people. Google's main business is advertising. So you can see how ad-blocking software collides with Google's business objectives. When Chrome was trying to be popular, it started allowing plugins like AdBlock Plus etc. Then slowly it started partnering with them for "Acceptable Ads Program" for a lot of money. Now after cementing its position as the most popular browser, Google is now coming down hard on ad blocking software. It is turning off a Chrome API (webRequest API) which most ad blocking plug-ins use to block ads.
Enter Pi Hole. This is an amazing use of Raspberry Pi which blocks ads before they enter your network. It keeps a blacklist of most popular ad serving domains …

IoT on Google Cloud Platform

Google wants people to use its Cloud Platform for connecting and managing IoT devices through IoT Core and use other GCP components like BigQuery to analyze data produced by those devices. While these products are fantastic, they also have some real world challenges.
IoT Core provides a managed service for connecting IoT devices. It talks with both HTTP and MQTT protocols and features one-click integration with Cloud PubSub easing most of the infrastructure tasks. However there are some limitations:
You cannot use any random MQTT topic to send/receive messages as you would expect on a custom MQTT bridge. There are special topic formats to send messages and also to receive commands.IoT Core uses Public-Private Key cryptography to secure devices. All IoT devices must first authenticate using the Public Key in a JWT token and then start sending and receiving messages. While these may seem like reasonable restrictions, one has to keep in mind that hardware vendors are still stuck in the 9…