A .NET Standard API for Elasticsearch providing CRUD operations, search queries, aggregations, and mapping support.
ElasticsearchCRUD is a .NET Standard library that provides a comprehensive API for interacting with Elasticsearch. It enables .NET developers to perform CRUD operations, execute complex search queries, manage indices, and handle document mappings directly from their C# code. The library simplifies integration with Elasticsearch by abstracting HTTP communication and offering a structured programming model.
.NET developers building applications that require full-text search, data indexing, or complex querying capabilities using Elasticsearch. It is particularly useful for those working with ASP.NET MVC, Web API, or Entity Framework who need a managed way to interact with Elasticsearch.
Developers choose ElasticsearchCRUD for its extensive feature set covering nearly all Elasticsearch APIs, its seamless integration with .NET ecosystems like Entity Framework, and its straightforward mapping system for complex document relationships. It reduces boilerplate code and provides a consistent, type-safe interface compared to raw REST calls.
Elasticsearch .NET netstandard API
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports nearly all Elasticsearch APIs including CRUD, advanced search with queries/filters/aggregations, and index management, as detailed in the extensive version history listing features like live reindexing and geo-shape mappings.
Offers attribute-based mapping for complex documents and built-in Entity Framework support for data transfer from SQL Server, making it a natural fit for ASP.NET MVC and Core applications, as shown in multiple tutorials.
Provides over a dozen blog posts and GitHub examples covering scenarios from basic CRUD to advanced use cases like parent-child documents and CSV exports, reducing the learning curve.
Includes efficient bulk inserts and live reindexing using scan and scroll, enabling performance optimizations and zero-downtime index updates, as demonstrated in Part 7 of the tutorials.
The project is maintained by one developer, which risks slower updates, limited support, and potential abandonment compared to community-driven alternatives like NEST.
Documentation is scattered across personal blog posts rather than a centralized site, making it harder to search and navigate for specific information or updates.
May not keep pace with new Elasticsearch releases; the README highlights support up to version 2.x, which could be outdated for projects requiring newer features or security patches.