It was a great pleasure speaking at Global Azure Bootcamp 2018 in Milwaukee last Saturday about Microsoft Azure Search service and also in meeting many Azure enthusiasts. Thanks for those who came out for the event and attended my session. You can find the links for code demos and presentation below and feel free to reach out to me if you have any questions or need help in implementing the Azure Search solution.
Azure Search Service is one of the powerful offerings in Azure that enables you to build powerful and comprehensive search engine features for enterprise applications which are normally harder to build on your own in traditional approach for complex, scalable and performance requirements. After implementing couple of search solutions using Azure Search, I wanted to write this post for sharing my view about how the implementation of search would look like in a production scenario
If you are building a modern web applications using Angular (Angular2 or Angular 2x) for client side, ASP.NET Web API for server side (web server) and IIS is hosting platform, you might be interested to understand the two build automation and deployment options. First, consider Angular UI and Web API as separate products and deploy their binaries separately into two different virtual directories. This is fairly straightforward approach and regular build process should just work. If
After a stint with AngularJS (version 1) in couple of projects, started exploring Angular2 and my immediate feeling is very positive. There were several reasons pushed the Angular team to build something completely new focusing on capabilities that enable developers to build scalable, high performant and cross platform applications as though AngularJS is powerful but lacks those important factors. Building modular application blocks is an essential aspect of any large-scale applications to increase the reusability,