The First Post
Finally, my custom blogging platform is ready and raring to go. I will try to write as frequently as I can and keep making platform improvements. Since I have been working on building my blogging platform for some time, I think my opening blog should talk about how the platform works.
First, the technology stack:
- Microsoft Azure Web App for MVC based user interface.
- Microsoft Azure Table Storage for storing blog content.
- Microsoft Azure Blob Storage for storing some platform resources and all media content of blog.
- Microsoft Azure Search Service for enabling search on the content.
- Microsoft Azure DocumentDb for capturing inputs from my site audience such as for Testimonials.
- Microsoft Azure Redis Cache for storing sessions and cache data.
- Analytics through Google and AppInsight.
- GitHub for source control.
Before I say anything else, I would like to say that you can find the whole source code available on my GitHub account. I would use MSDN and GitHub to post samples and you are free to use them, though, I would not mind link backs and comments as tokens of appreciation :)
Another point I would like to make here is that the whole infrastructure is running on low billing tiers, so if the quota gets consumed, you might encounter error pages. I will add capacity based on resource usage and whatever my budget can support. There will never be a donate button or advertisements on this site ever.
In a nutshell, the platform works as follows:
- I author content using the beloved Windows Live Writer.
- I push the content to the blog platform, in turn the platform does the following activities for me.
- It stores all the images and other media resources in Azure Blob Storage Service.
- It splits the content into small chunks and stores the chunks in Azure Table Storage Service. (Why? Because an entity in table storage can’t hold more than 64 KB of binary data)
- It uses Azure Search Service to index the content.
- You request for the content through search service or by navigating to the content.
- The platform pulls your requested data from the respective storage destinations.
- I cache certain content because querying for them repetitively is pretty expensive. You are served that content from the Azure Redis Cache.
For those who love diagrams, here is an image showing all the components.
There are other features available on the platform as well. I store all the data you supply though various forms in Azure DocumentDb. This gives me the flexibility to add\remove entities from data that I capture without writing any of those pesky DDL queries in SQL. Automatic indexing of data, flexible queries and out of the box connectivity to HDInsight though connectors are just some of the features for which I love DocumentDb. You should try it yourself to appreciate it better.
If you like a feature of the blog or want to copy a code snippet that I post in any article, feel free to do so. There are multiple ways to get in touch with me, feel free to use any. See you soon!
Your 2 cents
GET SMARTER!Stay up to date with interesting posts like these. Take a moment to subscribe!
- Continuous TeX Document Production with GitHub Actions
- IoT Edge Device Monitoring and Management with Azure Durable Entities Functions - Part 2
- IoT Edge Device Monitoring and Management with Azure Durable Entities Functions - Part 1
- Building a GraphQL Application with ASP.Net Core and TypeScript - Part 2
- Building a GraphQL Application with ASP.Net Core and TypeScript - Part 1