Azure Search is getting rolling and customers may have questions, or will have questions, about where it makes the most sense. First and foremost, doing Search is hard, and it can also be expensive. Azure Search is targeted at three core scenarios in this iteration:
Most customers of ecommerce applications/sites will find products by using search first. Azure Search fits nicely into this space with its range of features including filtering, category counts (faceting), scoring, filters, sorting, paging and projection.
User generated/social content
There are many different flavors of user-generated content applications, but most share similar requirements when it comes to search. Examples of these kind of applications include recipe sites, photo sharing sites, user-contributed news sites and social network applications that have a Web and mobile presence. These applications deal with a large volume of documents, sometimes many millions, particularly when they allow users to comment and discuss on items. Geo-spatial data is often involved, related to location of people or things. Relevance tends to be driven by text statistics in addition to domain-specific aspects such as document freshness and author popularity.
Users of line of business applications often navigate through their content using pre-defined menus and other structured access paths. However, when search is incorporated into these applications a lot of friction can be removed from general user interaction making it quicker and more efficient to retrieve this information.
Azure Search supports these scenarios from mobile devices to web sites and everything in between. A great introduction to using the cloud to provide app capabilities that used to be very hard in a quicker, easier fashion.
Check out the Azure Search blog post for more information/scenarios.