search

EOSIO / spec-repo

EOSIO Specifications Repository
MIT License
40 stars 8 forks source link

Separating concerns for enhanced database proposal #2

Closed b1bart closed 5 years ago

b1bart commented 5 years ago

Concern

The proposal in its current form conflates the resources that back the data access model with the data model itself. There is nothing inherently coupling about storing the existing data access model in physical RAM nor is there anything specifically enabling about the proposed KV storage that allows for physical disk based storage.

The means of storage is at best a cost trade off that developers can make if we present them with the option. Similar to Amazon S3 vs Amazon S3 Glacier.

I believe that instead of presenting a false choice we should address these two concerns with separate specifications instead of one conflated one.

tbfleming commented 5 years ago

I removed the text about RAM vs. SSD. We could add a new piece discussing that in the future.