[FEATURE] fitted DB instance for pullpiri

[leeeunkoo]

📝 Requirement Description

Due to performance limitations observed in the current ETCD-based database instance used by Pullpiri, it is required to replace the existing ETCD instance with a RocksDB-based instance. This change aims to improve read/write throughput, reduce latency, and enhance overall system stability under high-load conditions.

📋 Acceptance Criteria

• The RocksDB instance is successfully integrated and configured to replace the existing ETCD instance.
• Performance benchmarks show measurable improvement in read/write operations compared to ETCD.
• System stability and data consistency are maintained after migration.
• All dependent services operate normally without regression after the replacement.

📎 Related Documents/References

• Internal performance analysis report on ETCD bottlenecks (link to be added)
• RocksDB integration guide and configuration best practices (link to be added)
• https://github.com/eclipse-pullpiri/pullpiri/discussions/376[https://github.com/eclipse-pullpiri/pullpiri/discussions/376](url)

📌 Subtasks

🧪 Testing Plan

• Unit Test: Validate database interface compatibility and data integrity.
• Integration Test: Verify service interactions and transaction consistency with RocksDB.
• Performance Test: Measure throughput, latency, and resource utilization improvements.

📊 Test Results

---

[leeeunkoo]

@youngtaekiim main 머지할때 여기에 task 연결해서 진행하면 될것 같아요

[basheerFZ]

@leeeunkoo @youngtaekiim @daeyoung-jeong-lge
Please check this link for suggestion of using the etcd or redis or Berkely DB, this was proposal made by one of the opensource community members and the S-Core team rejected the same saying the DB cannot be ASILB certified or atleast the dependent libraries FFI.

eclipse-score/score#754 --> This is the proposal
Architecture note: This is basically specifying a key-value database. Instead of re-inventing the wheel for automotive ;) you could have a look at etcd. See https://etcd.io/ - This the configuration DB used by kubernetes. Since this DB can be distributed on multiple ECUs/hosts it could enable redundancy for all configuration data in a car if one of the big ECUs is out of action for some reason.

Here is the response / reply they are saying it is practically impossible, Its a matter of concern as we are also planning to migrate to rocksDB from etcd reason is performance reasons.

@steenlarsen, thank you so much for the hint provided. You are right, there are numerous key-value databases available as open source. Besides of etcd, there are e.g. Berkeley DB, Redis, ... However, none of them is certified for automotive according to ISO26262. As our application is required with an ASIL B, we must certify not just the application as such, but also all the libraries it depends on or at least prove their freedom from interference (basically the same effort). In case of etcd we find an impressive list under Libraries and tools. It would look similar for other DBs. Theoretically it might work out, practically from our experience - not feasible. Summary: automotive needs a wheel which fits to its requirements ;-).

but what exactly the reason they want to have their own DB implementation , how can they showcase their ASIL B or FFI. Please discuss this with @dongkyu once and let me know you guys opinion on the same. tomorrow when we want to contribute the pullpiri this should not be blocker call for us.

[daeyoung-jeong-lge]

@basheerFZ Thanks for the raising the expected issue on DB usage. :-)

@leeeunkoo @youngtaekiim @Chulhee1Lee @alivejun12 @yeohyeon-i
Basheer가 지적한 부분은 현재 ETCD를 포함한 다른 DB들 (아마도 RocksDB 조차도)이 ASIL 등급을 달성하지 못하였기 때문에, DB를 사용하는 우리 Pullpiri도 이에 영향을 받아 ASIL 등급을 달성하는데 어려움이 있을 수 있다는 것입니다. 이 부분이 문제가 되는지는 준영 책임님께서 확인해주셔야 할 것 같고요.
만약 ASIL-B의 DB가 필요하다면, 아마 차후에 S-Core의 Persistency (KVS)가 ASIL 등급을 달성할 것이니 이것으로 교체를 고려할 수도 있습니다. ASIL 등급을 달성하는 DB가 그리 많지는 않을 듯 하네요.

[alivejun12]

Period : 2025/12/11 00:00 ~ 2025/12/17 23:55 [Korea Standard Time] I am out of office. I will get back to you as soon as I return. thank you.

[alivejun12]

@basheerFZ
We have already reviewed the part of DB for safety certification of Eclipse-pullpiri.
If Eclipse-pullpiri have to include an open source DB, it would need to check Qualification of the DB or design it for Safety.

Ultimately, we are currently reviewing various options and will discuss them with a consulting firm for certification next year

1. Exclude open source databases from the Eclipse-pullpiri boundary
   ( DB usage is specified in the safety manual.)
2. Utilizing S-CORE Persistency

I will share any further later.