pjproject VS LiteDB

Hello, I'm in the process of developing a multiplayer FPS game and recently delved into ICE connectivity (STUN/TURN). Currently, my setup involves a custom matchmaking server in C++, with UDP port handling on the client side through UPnP or a fallback custom relay server. While the current approach works well, I'm exploring options to simplify the project by incorporating existing technologies. I've come across Libjuice and Libpjsip for NAT traversal. Libjuice offers a nice and simple API, but it supports only one person. Hence, I'm considering Libpjsip. I came across their ICE demo script at https://github.com/pjsip/pjproject/blob/master/pjsip-apps/src/samples/icedemo.c and I'm curious about its performance, particularly the pj_ice_strans_sendto2 function. I'm keen to understand how it compares to my current implementation with Berkeley Sockets and whether Libpjsip is a suitable choice for multiplayer P2P games. Any insights or assistance would be highly appreciated. Thanks!

Things improved a lot thanks to the adoption of the pjsip stack.

When I look at stuff like pjsip, I get the impression, it would be huge amount of work. Am I mistaken?

The first issue I'm facing is I can't find lib folder which is mentioned in Using pjproject libraries for your own application heading in the above-mentioned link. I download the source code from this link.

For client and server, I'm only really familiar with https://www.pjsip.org/. It also comes with a bunch of code for doing phone calls, which really most SIP Stacks were built around. But those parts can just not be used.

PJSIP (https://github.com/pjsip/pjproject) is used as SIP framework

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.

Maybe you want LiteDB? I don't think you need to write SQL, you can interact with the API.

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.

Please consider using the primary key to generate an unique value on the db side.

LiteDB

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.

[1] - https://github.com/mbdavid/LiteDB

[2] - https://github.com/linq2db/linq2db

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.