LiteDB
Netty
Our great sponsors
LiteDB | Netty | |
---|---|---|
11 | 53 | |
8,215 | 32,724 | |
- | 0.8% | |
8.0 | 9.5 | |
8 days ago | 4 days ago | |
C# | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LiteDB
-
Local migrations for embedded SQLite in F#
Personally, I used to use LiteDB which is a NoSQL version which in v4 paired very nicely with F# thanks to Zaid's lovely LiteDB.FSharp library. Sadly, when v5 showed up, a lot of the F# niceties were lost given how the API was changed and v5 was not very F# friendly. You can still use it of course but you fall back to more unsafe F# code which is not ideal.
-
Generic DB with minimal boilerplate code
Maybe you want LiteDB? I don't think you need to write SQL, you can interact with the API.
-
Yet another embedded DB (kind of)
Are you aware of LiteDB? It seems like your project is going for a very similar niche. Most people looking for this type of thing will probably go for the more mature and feature-rich solution (LiteDB). So if your project has some unique value proposition to distinguish it from LiteDB, you should elaborate on that.
-
How to introduce a queue for my API.
Please consider using the primary key to generate an unique value on the db side.
-
Unity MVVM
LiteDB
-
LiteDB: A .NET embedded NoSQL database
Before checking this out, people might want to take a look through the issues and pull requests of which there are 500+ and 50+ respectively [1]. I was really optimistic about this project and it was headed in a great direction, but it's not in a production ready state, and it seems that the main guy behind it has decided to move onto other things. It's been about a year since there was any significant activity.
I just mention this because a lot of these little issues might only become more apparent after integrating the db into your project and so it can be a bit annoying. I ended up swapping to Linq2DB [1]. It's something, more or less, similar offering an ORM/LINQ type system as well as the ability to also use direct SQL if desired. But the neat thing is that it also uses a standardized API for the LINQ query language, so you can do things like swap from SQLite to PostgreSQL in one* line of code, so long as you're not using any provider specific extensions.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
A mature NoSQL embedded/flatfile database like LiteDB would be nice. There are some similar Rust libraries but they aren't very close to production ready and the API tends to not be too user friendly. I had trouble finding one of these for a small app I had to write recently.
Netty
-
Reactor Netty: UDP DNS client example
Code of netty is here and using following library
- Netty: Asynchronous event-driven network application framework
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
We use Netty (https://netty.io/) as the source of the MQTT communication, and we build the MQTT features the MQTT broker should support ourselves on top of that.
-
Modern Async Primitives on iOS, Android, and the Web
In this space, we also have the somewhat related term blocking. Java's NIO library is one well-known non-blocking tool used for managing multiple tasks on a single Java thread. When listening to sockets, most of the time a thread is just blocked, doing nothing until it receives some data. So, it's efficient to use a single thread for monitoring many sockets, to increase the likelihood of the thread having some actual work to do. The Selector API does this but is notoriously challenging to program well. Instead, developers use frameworks like Netty which abstract some of NIO's complexity and layer on some best practices.
-
An investigative journey through concurrent data structures
DirectByteBuffer exhibits an intriguing behavior: it deallocates its backing memory during the finalization process, which occurs after garbage collection (GC) cycles. This poses an issue if your system is conservative with on-heap allocations, leading to infrequent GC cycles. In such cases, there could be a significant delay between the time the memory becomes unreferenced and when it is actually deallocated. This behavior could, in some respects, mimic a memory leak.
This is why some libraries hacks into DirectByteBuffer to deallocate memory explicitly, bypassing the finalizer altogether. For instance, the Netty library has implemented such a workaround, see Netty as an [example](https://github.com/netty/netty/blob/795db4a866401aa172757b95...).
-
Scaling to ~15K requests per second with Java – Part 1
Apologies replying to myself, but Netty, which underpins many of the popular Java backend frameworks, see backward compatibility as more important than supporting green threads.
https://github.com/netty/netty/issues/12816
It'll be interesting to see who (if anyone) picks up Netty's mantle in the Project Loom world.
-
Netty VS java-http - a user suggested alternative
2 projects | 25 May 2023
-
Is jre17 the problem? How do I get an old eclipse? Error: Could not find or load main class netty.DiscardServer Caused by: java.lang.ClassNotFoundException: netty.DiscardServer
Looks fairly recent so I'm glad I had a pre oct22 build https://github.com/netty/netty/issues/12737
-
What are your (favourite) Java best practices, personal tips, hints or just underrated stuff in general?
This is better? https://github.com/netty/netty/blob/4.1/pom.xml
-
Lessons learned from picking a Java driver for Amazon ElastiCache for Redis - Part 2
Given the fact that Lettuce is built with Netty, we also immediately noticed quite an impact on the initialization time (cold start) of our lambda function. Netty is really fast while executing, but takes a bit of time to initialize. The new Lambda Snapstart functionality might help with that.
What are some alternatives?
RavenDB - ACID Document Database
Undertow - High performance non-blocking webserver
MongoDB - The MongoDB Database
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Realm Xamarin - Realm is a mobile database: a replacement for SQLite & ORMs
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Apache Ignite - Apache Ignite
Grizzly
Event Store - EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures
KryoNet - TCP/UDP client/server library for Java, based on Kryo
DBreeze - C# .NET NOSQL ( key value store embedded ) ACID multi-paradigm database management system.
MINA - Mirror of Apache MINA