Upgrade to Pro — share decks privately, control downloads, hide ads and more …

4 Years Startup & Architecture

4 Years Startup & Architecture

Case study for architecture changes in startup company

Avatar for Motohiro Takayama

Motohiro Takayama

July 14, 2017
Tweet

More Decks by Motohiro Takayama

Other Decks in Technology

Transcript

  1. Architecture for 0→1 • MVA for MVP • DIY tiny

    architecture • &Not so huge Activity, reasonably small • Tightly coupled networking/model/view
  2. Growing Up • 1~3 years old • 2~5 engineers •

    (Original Members Gone (to other projects)
  3. Problem to Solve • Growth ↗↗↗ • Product requirements increased

    ↗ • A/B testing → code complexity ↗ • +"
  4. Problems • Τϯτϩϐʔͷ૿େ • Classes Getting bigger • ͍ΖΜͳ design

    pattern ͕ࠞࡏ • Getting harder to change • Hard for new members • ➡ ౷Ұ Architecture χʔζͷߴ·Γ
  5. Fork by Region • Problem to Solve • Region ಠࣗͷ

    UI, ࢪࡦΛ͢͹΍࣮͘૷ • ࣌ࠩͷ͋ΔίʔυϨϏϡʔΛ͠ͳ͍
  6. Architecture - • Component based • Project, ਓ͕૿͑ͯ΋ conflict ͠ͳ͍ɺׯব͠ͳ͍

    • Project ͝ͱʹ Component ͕͋ΔΠϝʔδ • Uber RIB ؾʹͳ͍ͬͯΔ • VIPER base, Android / iOS ڞ௨
  7. ͓ΘΓʹ • Startup ʹ࠷దͳ Architecture: phase ͰҟͳΔ • Scale to

    Product / Organization • ·ͩ࠷దղ͸ͳ͍ → ݟ͚ͭΑ͏ • We are hiring