TrinityCore VS FlatBuffers

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/

I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.

If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.

So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.

https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.

Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.

Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...

Much more in the discussion of this particular issue onGitHub: flatbuffers:Reverse engineering #4258

Related but not Rust-specific: FlatBuffers, Cap'n Proto.

If json files are a concern because of space, you can always look into something like protobuffers or flatbuffers. But whatever you use, you should try to find a solution where you don't have to think about the actual serialization/deserialization of your objects, and can just concentrate on the data.

Or, as an alternative to protobuffers, there's also flatbuffers, which is lighter weight and needs less memory: https://google.github.io/flatbuffers/

As the title suggests, I am considering using Flatbuffers as a way to parse sensor data that has been stored in local datafiles. The project language is python.