decide on technology stack & data architecture
TRANSCRIPT
![Page 1: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/1.jpg)
![Page 2: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/2.jpg)
Decide on Technology Stack & Data Architecture
Vishnu Gopal
![Page 3: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/3.jpg)
Where is your team now?
![Page 4: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/4.jpg)
1. You’ve Shortlisted an Idea2. You’ve got a clear
Product Narrative
![Page 5: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/5.jpg)
If you haven’t done all of those, please go back and complete those targets.
You can’t choose a technology stack without knowing what you’ll be building.
![Page 6: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/6.jpg)
Why is this important?
![Page 7: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/7.jpg)
1) A good technology stack can make or break version 1 of your
product.
![Page 8: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/8.jpg)
2) A simple “good enough” data architecture can lead to very fast
initial iterations.
![Page 9: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/9.jpg)
How is this done?
A: Technology Stack
![Page 10: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/10.jpg)
Basic Philosophy: Minimum Viable Technology
Review session by Ajay Shrivastava
![Page 11: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/11.jpg)
1) Pick “just enough” technology to build an alpha
![Page 12: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/12.jpg)
2) Do not plan forward too much.
![Page 13: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/13.jpg)
3) Use only technology you already know & are familiar with.
See Target: List Engineering Skills.
![Page 14: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/14.jpg)
4) Build according to your Product Narrative &
Low-fidelity Wireframe.
![Page 15: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/15.jpg)
5) Build the most important pieces first.
Note: for the purposes of Alpha, do not build a login &
signup workflow.
![Page 16: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/16.jpg)
How is this done?
B: Data Architecture
![Page 17: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/17.jpg)
Data Architecture = simple answer to: “Where is your data stored? What does each store contain?”
![Page 18: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/18.jpg)
No diagrams required at this stage.
![Page 19: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/19.jpg)
Example: “My data is mostly social media listings that I will store in MySQL”.
(Web App Example. After you scale, you can explore alternative data stores)
![Page 20: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/20.jpg)
Example: “My data is mostly stored in the mobile app in a SQLite DB”.
(Mobile App Example. After you scale, you can explore alternative data stores)
![Page 21: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/21.jpg)
Do not optimise data stores right now.
For 90% of cases, stick to a relational database.
MySQL or Postgres (Web) and SQLite (Mobile) is preferred.
![Page 22: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/22.jpg)
Todo: Submit a document which lists the stack chosen and the
data architecture.
![Page 23: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/23.jpg)
Check the Rubric for more information.
![Page 24: Decide on technology stack & data architecture](https://reader035.vdocuments.site/reader035/viewer/2022070521/58effb6d1a28ab6f4e8b45b5/html5/thumbnails/24.jpg)