# Shards are not splitted into smaller ones

**URL:** <https://forums.foundationdb.org/t/shards-are-not-splitted-into-smaller-ones/815>\
**Category:** Using FoundationDB\
**Created:** [October 29, 2018, 10:43am UTC](https://forums.foundationdb.org/t/shards-are-not-splitted-into-smaller-ones/815 "2018-10-29T10:43:52Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![spullara](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/spullara/32/125_2.png) [@spullara](https://forums.foundationdb.org/u/spullara)\
**Post date:** [October 30, 2018, 8:59pm UTC](https://forums.foundationdb.org/t/shards-are-not-splitted-into-smaller-ones/815/7 "2018-10-30T20:59:37Z")

</div>

I have been thinking about a meta-storage engine that would allow you to specify different storage engines for different ranges. I was thinking primarily that I would want that so I could have transactions that span a memory store and the SSD store but this might also be a use case for such a system.

---

_[View the full topic](https://forums.foundationdb.org/t/shards-are-not-splitted-into-smaller-ones/815)._