# Best practices for storing multiple logical records in one aerospike record?

**URL:** <https://discuss.aerospike.com/t/best-practices-for-storing-multiple-logical-records-in-one-aerospike-record/6249>\
**Category:** Query & Indexing\
**Tags:** aggregation\
**Created:** [May 15, 2019, 1:56pm UTC](https://discuss.aerospike.com/t/best-practices-for-storing-multiple-logical-records-in-one-aerospike-record/6249 "2019-05-15T13:56:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andersonbd1](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/andersonbd1/32/45_2.png) [@andersonbd1](https://discuss.aerospike.com/u/andersonbd1)\
**Post date:** [May 15, 2019, 1:56pm UTC](https://discuss.aerospike.com/t/best-practices-for-storing-multiple-logical-records-in-one-aerospike-record/6249/1 "2019-05-15T13:56:44Z")

</div>

We have a dataset in which we have more logical records than our current cluster capacity allows for. The records are really small, so it should be easy enough to group multiple records together into one aerospike record. I can obviously come up with a custom solution to do this, but I’m wondering if there are any best practices we should be following in doing this. I would think this is a fairly common problem.

---

<div class="post-metadata">

**Author:** ![pgupta](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/pgupta/32/2351_2.png) [@pgupta](https://discuss.aerospike.com/u/pgupta)\
**Post date:** [May 15, 2019, 3:18pm UTC](https://discuss.aerospike.com/t/best-practices-for-storing-multiple-logical-records-in-one-aerospike-record/6249/2 "2019-05-15T15:18:42Z")

</div>

Crossposted. Replied at: [Best practices for storing multiple logical records in one aerospike record? - Stack Overflow](https://stackoverflow.com/questions/56151150/best-practices-for-storing-multiple-logical-records-in-one-aerospike-record)