This repository has been archived by the owner on Mar 26, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Proposals
Javier Ardura edited this page Feb 26, 2019
·
10 revisions
The idea is propose the use of a local database to keep and send messages explaining their advantages and disadvantages.
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.
SOLID isolation, the most difficult part, maybe, of the chat.
- Dealing with database that is easy, familiar and provide a lot of info.
- Making a common chat where the database and handlers will be used as adapters.
- Solving 25MB POD's storage.
- Avoiding server use, that should be established, study its behavior and if the app become too big solving potential storage conflicts.
- Easiest to create first tests, just reading and writing a database.
- Model also used by Whatsapp to storage chats.
- Lot of tutorials available on the internet, becoming the decentralization the most difficult part.
- It isn't a solution, just a delegation.
- Delegation of the storage releasing to the handlers.
- Running slowdown.
- Difficulties to include the database with the programming language.