Indexing and searching NuGet.org with Azure Functions and Search
summary
Builds a working reverse package search that maps public type names to NuGet packages, implemented as a pipeline: a custom NuGet catalog trigger watches the v3 catalog, pushes package ops to queues, a downloader saves nupkgs, an indexer uses System.Reflection.Metadata to extract public types and namespaces, and results land in an Azure Search index queried by a ReSharper quick fix. Full index processes ~2–2.6M packages (reportedly ~3.5 TB) and a rebuild takes ~12–14 hours on B1 machines; the pipeline is proven and operational.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:25Find this type on NuGet
- 4:55NuGet Serverside API
- 7:37Catalog
- 13:24Building a new version
- 15:04Creating a timer function
- 18:32Azure Functions and best practices
- 23:21Creating a custom trigger binding
- 25:04What is a catalog trigger
- 33:49Downloading packages
- 37:38Indexing packages
- 44:18Web API
related talks
59mIndexing and searching NuGet.org with Azure Functions and Search
11mTotal Rewrite: A Story About F# and Azure Functions in Production
25mBuilding AI-Powered Applications with Azure Serverless Functions and C# .NET
53mUsing F# on Azure Functions in Production
47mAzure Functions PowerShell: The Missing Manual
25mCloud for Frontend
42mServer-less compute with .NET based Azure Functions
44mHop on the serverless adventure