TrinityCore VS MessagePack

You could take a look at TrinityCore[1] and adjacent projects! Best of luck!

[1] https://github.com/TrinityCore/TrinityCore

TrinityCore: https://www.trinitycore.org/ send email for your questions, or look at this video if you want https://www.youtube.com/watch?v=tAJ0dvNuARs

Trinitycore has 3.4.0 for Wotlk classic but it's pure sandbox. It's so much work to be done so don't expect it to be released. https://github.com/TrinityCore/TrinityCore/tree/wotlk_classic

You can host your own WoW server locally! I would personally recommend TrinityCore. It can be a little bit of a hassle, here's a setup guide.

If they use the base TrinityCore code there's no processing (the whole point of GetAll is a minimal processing dump of the data as-is). You can see the commit for it here https://github.com/TrinityCore/TrinityCore/commit/3aaeb574050668e5a240078f6e40337c3975d110 and you can see it just dumps what is there until 55k then stops hard.

You can just compile one here - https://github.com/TrinityCore/TrinityCore

TrinityCore, AzerothCore- C++, these and others like them are the server for projects- well-known for being used on private WOW servers, so they're probably good enough for your personal project https://www.libhunt.com/r/TrinityCore - https://www.trinitycore.org/ - https://www.azerothcore.org/

so appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls?

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing.

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto.

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages.

I'll try that msgpack.org website.

First of all, you're comparing this to GSON and Kryo, how does it compare to Msgpack, fast-serialization, but also Elsa and I'm sure, many others? Are there any limitations and/or trade-offs?

Upvote for msgpack, one of the great undervalued message protocols available.

I have two suggestions Capnproto, MessagePack (those are only the two examples that came to mind first, i bet there are even one or two especially developed for rust). Both of these are better than json in nearly every way.

Encode messages as JSON or MessagePack.