ZAP C++

ZAP C++ is the ZAP Protocol's implementation of ZAP, a data serialization and RPC framework focused on performance and usability.

Why ZAP C++?

Traditional serialization formats like JSON, XML, or even Protocol Buffers require encoding data into bytes and then decoding it back. This process takes time and allocates memory.

ZAP C++ takes a different approach: data is stored in a format that can be directly used without parsing. When you receive a message, you can immediately access any field without first scanning through the entire message.

Key Advantages

Zero-Copy Design

Messages can be memory-mapped directly from disk or network buffers. No copying or parsing required. This makes ZAP C++ ideal for:

• Memory-mapped databases
• High-frequency trading systems
• Real-time communication
• Embedded systems with limited resources

Schema Evolution

ZAP C++ schemas can evolve over time while maintaining both forward and backward compatibility:

• New fields can be added to any struct
• Old code can read new messages (ignoring new fields)
• New code can read old messages (using defaults for missing fields)

Capability-Based Security

The RPC system implements object-capability security. Instead of checking permissions at every operation, capabilities (references to objects) are passed around. If you have a reference, you have permission to use it.

Promise Pipelining

When making an RPC call that returns an object, you can immediately make calls on that object without waiting for the first call to complete. The system automatically pipelines these requests, reducing latency.

Architecture Overview

ZAP C++ consists of several components:

Comparison with Other Formats

*ZAP C++ includes a text format for debugging and configuration files.

Next Steps

• Follow the Installation Guide
• Learn the Schema Language
• Understand Serialization
• Explore the RPC System