Skip to content
This repository has been archived by the owner on Mar 26, 2022. It is now read-only.

Proposals

Javier Ardura edited this page Feb 26, 2019 · 10 revisions

02/26/2019

Local database use proposal

Introduction

The idea is propose the use of a local database to keep and send messages explaining their advantages and disadvantages.

Idea

Using any kind of database to:

  • POD reading keeping messages into the database.
  • Also keeping sent messages to load it easiest.
  • Create a smart database controller, who is able to reading and writing on the pod.

Advantages

SOLID isolation, the most difficult part, maybe, of the chat.

  1. Dealing with database that is easy, familiar and provide a lot of info.
  2. Making a common chat where the database and handlers will be used as adapters.
  3. Solving 25MB POD's storage.
  4. Avoiding server use, that should be established, study its behavior and if the app become too big solving potential storage conflicts.
  5. Easiest to create first tests, just reading and writing a database.
  6. Model also used by Whatsapp to storage chats.
  7. Lot of tutorials available on the internet, becoming the decentralization the most difficult part.

Disadvantages / doubts

  1. It isn't a solution, just a delegation.
  2. Delegation of the storage releasing to the handlers.
  3. Running slowdown.
  4. Difficulties to include the database with the programming language.
Clone this wiki locally