In this post, I want to cover Azure Search from a different perspective and share some details that might help people getting starting in the exciting world of search. The main focus will be on pointing out the underlying technology, helping you to understand better and build search solutions.
The Microsoft Azure Search team recently released a new preview version, which includes some exciting new features. I’ve briefly covered them in my previous Azure Search Services post but wanted to dive a bit deeper into the Indexers.
An indexer is a content crawler written for a specific data source eliminating the need for writing code responsible for extract data from your data source and feed this data within the index. The Indexer runs within the Azure context, and it’s therefore not required to create a service for hosting this process (billing details are not available yet).
This post will offer some insights on how to index popular document formats like Word, PDF, and JPG’s when using the Azure Search offering. Azure Search is currently in preview and therefore evolving rapidly. However, as for now, indexing documents isn’t supported. Hence my search for alternative ways of extracting document data and metadata.
After seeing how many other applications are dealing with Azure Blob storage, I’ve discovered a couple of standard practices when it comes to the creation of a storage hierarchy, along with some performance and security considerations. I haven’t found a lot of insights regarding this topic and therefore decided to write something down.
Within this post, I will focus on the basics of Availability and Performance monitoring within the Azure preview portal. This includes the creation of custom dashboards, adding and altering charts, enabling diagnostics and creating alerts.
This post is a follow-up post to my previous post Optimizing WordPress hosted on Windows.
It’s the holiday season and therefore having some time to spare, I thought I might as well include the part I left out my previous post. Therefore this post focuses solely on including Azure CDN within your WordPress environment using the W3 Total Cache WP plugin.
I was recently working on some performance issues, which also included dealing with the web front-end. I’m more of a middleware/backend guy, however, do know my way around web development and website optimization (minification, bundling, caching, Gzip, CDN, etc.)
After working on the issues, I was wondering how my blog would perform. I’ve never run any analysis, leave alone applied any tweaks. This website is a basic out of the box WordPress installation (scripted by discountasp.net) hosted on Windows containing only a hand full of articles. And therefore not even thinking about possible performance issues, but I was wrong.
Recent Comments