Decide on Technology Stack & Data Architecture

Vishnu Gopal

Where is your team now?

1. You’ve Shortlisted an Idea2. You’ve got a clear

Product Narrative

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.

Why is this important?

1) A good technology stack can make or break version 1 of your

product.

2) A simple “good enough” data architecture can lead to very fast

initial iterations.

How is this done?

A: Technology Stack

Basic Philosophy: Minimum Viable Technology

Review session by Ajay Shrivastava

1) Pick “just enough” technology to build an alpha

2) Do not plan forward too much.

3) Use only technology you already know & are familiar with.

See Target: List Engineering Skills.

4) Build according to your Product Narrative &

Low-fidelity Wireframe.

5) Build the most important pieces first.

Note: for the purposes of Alpha, do not build a login &

signup workflow.

How is this done?

B: Data Architecture

Data Architecture = simple answer to: “Where is your data stored? What does each store contain?”

No diagrams required at this stage.

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)

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)

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.

Todo: Submit a document which lists the stack chosen and the

data architecture.

Check the Rubric for more information.