# Dapps architecture in the near future?

**URL:** <https://discuss.ipfs.tech/t/dapps-architecture-in-the-near-future/438>\
**Category:** Help\
**Created:** [May 23, 2017, 12:21am UTC](https://discuss.ipfs.tech/t/dapps-architecture-in-the-near-future/438 "2017-05-23T00:21:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 12:21am UTC](https://discuss.ipfs.tech/t/dapps-architecture-in-the-near-future/438/1 "2017-05-23T00:21:10Z")

</div>

_From @pavetok on Sat Jun 11 2016 15:58:42 GMT+0000 (UTC)_  
  
Dapps architecture in the near future?

| Platform | Write data store | Read data store | Data store API |
| --- | --- | --- | --- |
| “plain old” browser | event-log-like (IPFS) | blockchain-like ( IPFS) | HTTP |
| electron app | blockchain-like (IPFS) | key-value-like (IPFS) | JavaScript |
| ipfs browser | key-value-like (IPFS) | sqlite-like | something else? |
| something else? | something else? | pouchdb-like | |
| | | something else? | |
|   
  
_Copied from original issue: [Dapps architecture in the near future? · Issue #133 · ipfs-inactive/faq · GitHub](https://github.com/ipfs/faq/issues/133)_ | | | |