# Keeping Delivery Executions as Key Value

**URL:** <https://forum.community.taotesting.com/t/keeping-delivery-executions-as-key-value/116>\
**Category:** General\
**Created:** [May 26, 2026, 4:51am UTC](https://forum.community.taotesting.com/t/keeping-delivery-executions-as-key-value/116 "2026-05-26T04:51:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![qaimkhan](https://avatars.discourse-cdn.com/v4/letter/q/e79b87/32.png) [@qaimkhan](https://forum.community.taotesting.com/u/qaimkhan)\
**Post date:** [May 26, 2026, 4:51am UTC](https://forum.community.taotesting.com/t/keeping-delivery-executions-as-key-value/116/1 "2026-05-26T04:51:01Z")

</div>

Hi Everyone,

We are using Tao for large group of users (more than 1000). Initially it wasn’t for more than 300 but then we switched the Delivery Execution to KV instead of Ontology. So far it works fine and the performance is immensely optimised.

Are there any side effects of shifting from Ontology to KV? What are your recommendations when using KV mode?

---

<div class="post-metadata">

**Author:** ![Cicatrice](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/cicatrice/32/31_2.png) [@Cicatrice](https://forum.community.taotesting.com/u/Cicatrice)\
**Post date:** [June 11, 2026, 5:32pm UTC](https://forum.community.taotesting.com/t/keeping-delivery-executions-as-key-value/116/2 "2026-06-11T17:32:08Z")

</div>

Hello, thanks for contacting us!

It seems you are refering to persistences configuration for TAO Core.

TAO Core is our legacy version of TAO found in [GitHub - oat-sa/tao-core: main extension of TAO · GitHub](https://github.com/oat-sa/tao-core)

While TAO Core is now a part of TAO Community Edition, only the authoring features from TAO Core are supported here. TAO Community Edition comes with its own Delivery engine, which now use ElasticSearch as backend.

You are free to continue using TAO Core, of course, but support here is limited.

For Delivery Execution, it is totally possible to use KeyValue storage instead Ontology. However, you will have to ensure your KV engine (e.g. Redis) has proper data retention policy and backups to recover in case of failure.