- Traditional relational model?
- Relational databases tend to fragment data into lots of small pieces. For example, consider an order with order items; each order item will be a separate record in a table.
- In a distributed system like RAMCloud, each fragment is likely to end up on a different server, resulting in lots of requests to collect an interesting amount of data.
- The distribution also exacerbates consistency issues during updates.
- Opaque variable-length blobs, like memcached?
- Hierarchical hashes (JSON, Fiz datasets)?
- In this model an entire order, including the main order and its items, would be a single object stored on a single server.
- Should RAMCloud be designed for small objects only? Any upper limit on size?
Manage space
Manage content
Integrations