eCAL
FlatBuffers
eCAL | FlatBuffers | |
---|---|---|
11 | 48 | |
1 | 22,062 | |
- | 0.6% | |
9.2 | 8.7 | |
almost 2 years ago | 4 days ago | |
C++ | C++ | |
Apache License 2.0 | 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.
eCAL
-
eCAL ipc framework
New version (5.94) of the high performance interprocess / interhost communication framework eCAL is available. eCAL supports different transport layer like shared memory for interprocess and udp multicast for interhost communication. It does not force the user to use a specific serialization format but supports some of the standards like google protobuf, capnproto or flatbuffers. The API is wrapped to C, C++, Python, C#, Rust and Go (the last two I never tested ;-)). Here you can find all the documentation. Check out the great applications for monitoring, record and replay. eCAL is Apache 2 licensed, repository hosted here. Have fun :-)
- eCAL 5.9.4 released
-
Should I run ROS on windows, through WSL or on linux with dual boot?
I you just need a fast publish / subscribe framework for windows you can give eCAL a try. The setup is done in less a minute and their is no dependency hell. Just to mention it as alternative. Documentation here
-
Google Protobuf vs JSON vs [insert candidate here]
I would concider using eCAL since it blasts everything out of the water in terms of performance and comes with some handy tooling for inspection of messages in-travel.
-
eCAL 5.9.0 released
Source on GitHub: https://github.com/continental/ecal
-
Sender and Receiver implementations
Check out eCal.
-
grpc_bench: open-source, objective gRPC benchmark
This really makes me want to try https://github.com/continental/ecal with https://github.com/google/flatbuffers to see how they compare. I also know that gpc for cpp at least stops functioning by about 4 MB of request size. Which I find stupid. What if I want to send uncompressed bitmaps!
-
Announcing Eclipse iceoryx 1.0.0
Congratulations. Well done. eCAL will update as soon as possible to the new release. The new custom header and the n:m pub/sub support are really welcome new features.
-
Open source developers that work outside of a full time job, what motivates you?
Here is their counter callback example: https://github.com/continental/ecal/blob/master/samples/cpp/counter/counter_rec_cb/src/counter_rec_cb.cpp
FlatBuffers
- FlatBuffers – an efficient cross platform serialization library for many langs
-
Cap'n Proto 1.0
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-...
-
Anyone has experience with reverse engineering flatbuffers?
Much more in the discussion of this particular issue onGitHub: flatbuffers:Reverse engineering #4258
-
Flatty - flat message buffers with direct mapping to Rust types without packing/unpacking
Related but not Rust-specific: FlatBuffers, Cap'n Proto.
- flatbuffers - FlatBuffers: Memory Efficient Serialization Library
-
How do AAA studios make update-compatible save systems?
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.
- QuickBuffers 1.1 released
-
Choosing a protocol for communication between multiple microcontrollers
Or, as an alternative to protobuffers, there's also flatbuffers, which is lighter weight and needs less memory: https://google.github.io/flatbuffers/
- FlatBuffers: FlatBuffers
-
Is using Flatbuffers to parse sensor data a bad application of 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.
What are some alternatives?
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Protobuf - Protocol Buffers - Google's data interchange format
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]
cyclonedds - Eclipse Cyclone DDS project
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
nanomsg - nanomsg library
cereal - A C++11 library for serialization
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec