...

collections/solutions/infra/solution.md

@@ -0,0 +1,53 @@
+# Solution
+
+We need to work in steps and go careful to resolve the issues
+
+## Phase 1
+
+- Do crowdfunding from TF DMCC ([see here](redz/crowdfunding/cf.md))
+  - This crowdfunding will pay for cloud services (see below)
+- TF Senior Consultants help    
+  - e.g. Jan, Azmy, Thabet, Lee
+  - fix and improve issues. This service will be free.
+- ThreeFold will host the solution on its decentralized and add required capacity fees will be
+  - 10 USD per TB (2.5x less compared to Amazon, ...) transfer
+  - 5 USD per TB stored
+  - 0.1 USD per user per month
+- ThreeFold helps to run the operations
+  - will help build all required procedures.
+  - will help build monitoring solution for infra and bandwidth
+  - all will be documented in git based private repositories
+- ThreeFold will decentralize in such a way to provide following benefits.
+  - better uptime
+  - more performance
+  - less chance to be shutdown
+- **ThreeFold will reach out to own network and help with crowd funding**
+
+
+## Phase 1.1
+
+Decentralized the current solution with minimal change for the appl developers, aim is to support 10m people.
+
+- operational requirements
+  - good backups on current DB
+  - automatic daily restore on 2 chosen locations, these DB's are available but read only, so we know backup works
+- technical improvements
+  - use geo DNS to make sure customers have best possible accesstime
+  - use redis as pub/sub mechanism, help developers to make change
+  - install decentralized redis (so available in all locations)
+  - host web front ends on +20 location capable to deal with load upto 10m people
+  - roll out our own CDN on +20 locations
+
+## Phase 1.2
+
+Help developers to create the solution for 2.0 which will provide all required benefits.
+
+Help RedZ with legal and financial advice, see which structures to create to provide safety for the team. Use legal team who is already working with TF.
+
+## Phase 2.0
+
+Introduce the Digital Twin concept and roll out the solution of the future which will introduce unlimited freedom while maintaining minimal required responsibility.
+
+We believe phase 2 has the biggest chance to resolve the issues as mentioned before.
+
+> [see solution in more detail here](redz/solution/solution_vs_issues.md)

collections/solutions/infra/solution_vs_issues.md

@@ -0,0 +1,47 @@
+
+# Solutions in relation to Issues
+
+## high CDN cost = Content Delivery
+
+- cost goes to 10 USD at start, from v2.0 can be even lower.
+ 
+## High cost of operations
+
+- ThreeFold has developed a self healing capable system which can be adjusted for the operrations of RedZ.
+
+## Ability to be shut down on the public cloud
+
+- from v2.0 it will be extremely difficult to shutdown this service.
+
+## App not ready to scale
+
+- There is no scalability limit to v2.0, it can scale to billions.
+
+## Ability to shutdown the mobile apps
+
+- one app will be called TFConnect and will be the app running the peer2peer network Mycelium, identity management, reputation management, reliable message bus, geo dns, content caching,... TFConnect will be available for all major desktop and mobile platforms.
+- Then there will be multiple apps which can be native and web, the apps will talk to TFConnect on the device or desktop.
+- We suggest to also develop a rich web app which connects on the Phone to TFConnect, this cannot be blocked and would be ideal fall back solution in case the native mobile app gets blocked. Current web technology can be made in such a way it would act almost the same compared to native, thanks to TFConnect it would still be fast and highly responsive.
+
+## GDPR
+
+- By design resolved in 2.0, all data is owned by the user.
+
+## Legal potential trouble
+
+- Resolved by consultancy from TF, it can be done but is not trivial.
+
+## Redundancy / Uptime
+
+- v2.0 is 100% redundant and should never be able to go down.
+
+## Performance
+
+- v2.0 works as local as it can, providing best possible performance, as the network grows performance will be better for the users.
+
+## protect against human error
+
+- good procedures and using more of our self healing tech might help here.
+
+
+