Post #2533366
2026-03-26 18:26 UTC
Now we have a system where we publish, sync and persist operations grouped by topics on top of any p2p network.
With this data being available to us now we want to make sure to correctly process and stream it towards the application layer. For this we're borrowing many conceps from general "event streaming" theory, you might know this from NATS JetStream, Kafka or something like that, with the difference that we're not aiming for "big data centres" but decentralised and autonomous p2p networks.
Replies (1)
-
@p2panda@autonomous.zone 2026-03-26 18:26
When being subscribed to a topic you have something like a stateful "stream consumer" now. Every operation which runs through that stream gets processed, first on an internal system-layer where we check the log-integrity, prune the log on demand, order operations causally and later we'll also decrypt them here. After this we're forwarding the message to your application-layer, with a bunch of meta data and debugging info attached.