cbor-java
Cap'n Proto
Our great sponsors
cbor-java | Cap'n Proto | |
---|---|---|
17 | 66 | |
116 | 11,180 | |
- | 1.6% | |
6.6 | 9.2 | |
3 days ago | 5 days ago | |
Java | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
cbor-java
-
Amazon Ion Specification
What's the pros and cons of this versus CBOR, which we had great success with in our system.
https://cbor.io
-
Compressing GraphQL Global Node ID
CBOR (Concise Binary Object Representation) is a codec for small JSON object, similar to MessagePack but in the internet standard.
-
Why is json logging the “standard”?
JSON is a simple key=value pair representation. If you want to implement it by your hand with the same set of features (maps, lists, character escaping) then you will get something really similar. They are binary alternatives like https://cbor.io/ , but they are not popular for same reasons we use human readable representation of data for any other use case in programming
- RFC 8949 Concise Binary Object Representation
-
What’s everyone is using for framing and serialising data
CBOR
-
Alternatives to JSON and gjson as a document datastore?
Maybe this? http://cbor.io/ Haven't used it personally but I've read good things about it and the documentation makes sense.
-
go-cose: CBOR Object Signing and Encryption
go-cose is the Go implementation of COSE. COSE is a signing and encryption format based on the Concise Binary Object Representation format (CBOR). While inspired by the needs of the IoT community including fast processing on low-memory devices, the format is broadly applicable from small devices to large-scale server environments. COSE has incorporated lessons learned from Javascript Object Signing and Encryption (JOSE) efforts including JSON Web Signature (JWS) and JSON Web Token (JWT).
-
MQTT lightweight variable payload
Have a look at cbor, https://cbor.io/ It's very compact and works wonderfully for embedded devices. Works identical to Json but than for binary data.
-
JSON Storage Efficiency
You could also look into CBOR serialization format. It's less readable but it's much more efficient than JSON.
- CBOR – RFC 8949 Concise Binary Object Representation
Cap'n Proto
-
Mysterious Moving Pointers
Yeah I pretty much only use my own alternate container implementations (from KJ[0]), which avoid these footguns, but the result is everyone complains our project is written in Kenton-Language rather than C++ and there's no Stack Overflow for it and we can't hire engineers who know how to write it... oops.
[0] https://github.com/capnproto/capnproto/blob/v2/kjdoc/tour.md
-
Show HN: Comprehensive inter-process communication (IPC) toolkit in modern C++
- may massively reduce the latency involved.
Those sharing Cap'n Proto-encoded data may have particular interest. Cap'n Proto (https://capnproto.org) is fantastic at its core task - in-place serialization with zero-copy - and we wanted to make the IPC (inter-process communication) involving capnp-serialized messages be zero-copy, end-to-end.
That said, we paid equal attention to other varieties of payload; it's not limited to capnp-encoded messages. For example there is painless (<-- I hope!) zero-copy transmission of arbitrary combinations of STL-compliant native C++ data structures.
To help determine whether Flow-IPC is relevant to you we wrote an intro blog post. It works through an example, summarizes the available features, and has some performance results. https://www.linode.com/blog/open-source/flow-ipc-introductio...
Of course there's nothing wrong with going straight to the GitHub link and getting into the README and docs.
Currently Flow-IPC is for Linux. (macOS/ARM64 and Windows support could follow soon, depending on demand/contributions.)
-
Condvars and atomics do not mix
FWIW, my C++ toolkit library, KJ, does the same thing.[0]
But presumably you could still write a condition predicate which looks at things which aren't actually part of the mutex-wrapped structure? Or does is the Rust type system able to enforce that the callback can only consider the mutex-wrapped value and values that are constant over the lifetime of the wait? (You need the latter e.g. if you are waiting for the mutex-wrapped value to compare equal to some local variable...)
[0] https://github.com/capnproto/capnproto/blob/e6ad6f919aeb381b...
- Cap'n'Proto: infinitely faster than Protobuf
-
I don’t understand zero copy
The second one is to encode data in such a way that you can read it and operate on it directly from the buffer. You write data in a layout that is the same, or easily transformed as types in memory. To do that you usually need to encode with a known schema, only Sized types to efficiently compute fields locations as offsets in the buffer, and you usually represent pointers as offset into the encode. You can look at capnproto protocol for instance https://capnproto.org/
-
OpenTF Renames Itself to OpenTofu
Worked well for Cap'n Proto (the cerealization protocol)! https://capnproto.org/
-
A Critique of the Cap'n Proto Schema Language
With all due respect, you read completely wrong.
* The very first use case for which Cap'n Proto was designed was to be the protocol that Sandstorm.io used to talk between sandbox and supervisor -- an explicitly adversarial security scenario.
* The documentation explicitly calls out how implementations should manage resource exhaustion problems like deep recursion depth (stack overflow risk).
* The implementation has been fuzz-tested multiple ways, including as part of Google's oss-fuzz.
* When there are security bugs, I issue advisories like this:
https://github.com/capnproto/capnproto/tree/v2/security-advi...
* The primary aim of the entire project is to be a Capability-Based Security RPC protocol.
- Cap'n Proto: serialization/RPC system – core tools and C++ library
-
Sandstorm: Open-source platform for self-hosting web app
I like how they use capability-based security [0] and use Cap'n Proto protocol. This is another technology that is slow to get broad adoption, but has many things going for when compared to e.g. Protocol Buffers (Cap'n Proto is created by the primary author of Protobuf v2, Kenton Varda).
[0] https://sandstorm.io/how-it-works#capabilities
[1] https://capnproto.org
-
Flatty - flat message buffers with direct mapping to Rust types without packing/unpacking
Related but not Rust-specific: FlatBuffers, Cap'n Proto.
What are some alternatives?
simd-json - Rust port of simdjson
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
plutus-starter - A starter project for Plutus apps
Protobuf - Protocol Buffers - Google's data interchange format
plutus-pioneer-program - This repository hosts the lectures of the Plutus Pioneers Program. This program is a training course that the IOG Education Team provides to recruit and train software developers in Plutus, the native smart contract language for the Cardano ecosystem.
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
jsoniter - jsoniter (json-iterator) is fast and flexible JSON parser available in Java and Go
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
plutus - The Plutus language implementation and tools
Apache Thrift - Apache Thrift
Alonzo-testnet - repository for the Alonzo testnet
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]