SqliteCache for ASP.NET Core Alternatives

Similar projects and alternatives to SqliteCache for ASP.NET Core

Akavache

3 2,414 8.1 C# SqliteCache for ASP.NET Core VS Akavache

An asynchronous, persistent key-value store created for writing desktop and mobile applications, based on SQLite3. Akavache is great for both storing important data as well as cached local data that expires.
Lazy Cache

9 1,690 0.0 C# SqliteCache for ASP.NET Core VS Lazy Cache

An easy to use thread safe in-memory caching service with a simple developer friendly API for c#
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
FusionCache

9 1,285 8.8 C# SqliteCache for ASP.NET Core VS FusionCache

FusionCache is an easy to use, fast and robust cache with advanced resiliency features and an optional distributed 2nd level.
CacheManager

3 2,320 0.0 C# SqliteCache for ASP.NET Core VS CacheManager

CacheManager is an open source caching abstraction layer for .NET written in C#. It supports various cache providers and implements many advanced features.
SharpRepository

0 655 0.0 C# SqliteCache for ASP.NET Core VS SharpRepository

C# Generic Repository for use with Entity Framework, RavenDB and more with built-in caching options.
Fine Code Coverage

1 485 9.4 C# SqliteCache for ASP.NET Core VS Fine Code Coverage

Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
EasyCaching

1 1,847 6.8 C# SqliteCache for ASP.NET Core VS EasyCaching

:boom: EasyCaching is an open source caching library that contains basic usages and some advanced usages of caching which can help us to handle caching more easier!
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Cache Tower

2 579 4.8 C# SqliteCache for ASP.NET Core VS Cache Tower

An efficient multi-layered caching system for .NET
monkey-cache

2 657 4.4 C# SqliteCache for ASP.NET Core VS monkey-cache

Easily cache any data structure for a specific amount of time in any .NET application.
Wkhtmltopdf.NetCore-deprecated

0 214 0.0 C# SqliteCache for ASP.NET Core VS Wkhtmltopdf.NetCore-deprecated

Discontinued Rotativa + Net Core
sqlite-readers-writers

1 1 10.0 Rust SqliteCache for ASP.NET Core VS sqlite-readers-writers

An SQLite benchmark for concurrent readers and writers
NCache

1 635 0.0 C# SqliteCache for ASP.NET Core VS NCache

NCache: Highly Scalable In-Memory Distributed Cache for .NET

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better SqliteCache for ASP.NET Core alternative or higher similarity.

Suggest an alternative to SqliteCache for ASP.NET Core

SqliteCache for ASP.NET Core reviews and mentions

Posts with mentions or reviews of SqliteCache for ASP.NET Core. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-25.

Storing query results
3 projects | /r/dotnet | 25 Jun 2023

For pure key-value storage .net has IDistributedCache abstraction, with SQLite implementation. (This has no dependencies on asp.net core and can be used in any .net app)
In pursuit of the best value US cloud provider
2 projects | news.ycombinator.com | 23 Apr 2023

This has been posted and reposted continuously for a year and I still don’t understand the comparisons in the article. Either use SQLite across the board or use MySQL/Postgres across the board. Or do both. You can even model a self-managed rdbms install on the clouds that don’t have that turnkey offering. But mixing and matching makes no sense.
I’m a huge fan of SQLite and have open sourced some .NET stuff around it (eg https://github.com/neosmart/AspSqliteCache ) but learned a very expensive mistake in using it for an ASP.NET Core Project with the default pattern (i.e. with EF Core).
SQLite locks (tables or the entire db depending on configuration) upon write. If you use shared cache mode and WAL you can get very far with one write thread and many competing reads - depending on shared cache mode, WAL, and other options. I benchmarked the different configurations with one or more writing threads here to show how it scales: https://github.com/mqudsi/sqlite-readers-writers
But this approach is hard to model with EF Core. If you use the default request-scoped DI injected connection, you risk any writes upgrading the read lock to a write lock for the duration of the request. The better approach is to use the default request-scoped connection for RO operations and then request a scoped/transient DI connection for any write ops, but copying internal EF entity tracking state from one EF instance to another is tedious and fraught with issues. You’re at least able to work around this if you try to always keep in mind write transaction lifetimes, though.
The problem comes as soon as you need a “background service” in the sense of “an operation running independently of requests and parallel to them.” If that service needs a write lock for any amount of time, you’re suddenly going to be seeing write timeouts (since default behavior is to poll repeatedly until a write lock is obtained) and that is pretty much impossible to fix.
As one of the biggest advantages of using a resident executor like .NET or Java vs a per-request stateless option like PHP is that you can do stuff independent of requests, SQLite is tricky to use correctly in prod in this model.
The good news is that if you use the SQLite EF provider and run into this, it’s usually not too hard to switch to a real DB provider as a lot of the work is abstracted.