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

Tuist, 도입은 했는데 그래서 Modular Architecture 는 어떻게 ...

Wooseong Kim
October 17, 2023
Programming
0
340

Tuist, 도입은 했는데 그래서 Modular Architecture 는 어떻게 만들어 가나요?

Let'Swift 2023 에서 Tuist 기반으로 Modular Architecture 를 점진적으로 만들어 나가는 과정을 소개합니다.

Wooseong Kim

October 17, 2023
Tweet

More Decks by Wooseong Kim

See All by Wooseong Kim
Modular Architecture w/ Tuist
innocarpe
0
530
Test-Driven-Development with ReactorKit in StyleShare
innocarpe
1
880
Async network logic testing using Protocol (Test Stub)
innocarpe
2
360
Developing iOS with Rx, MVVM
innocarpe
1
150
git + Pull Request + Code Review and Project Management with Agile
innocarpe
0
69
Online Board(Trello), Scrum(Pivotal Tracker), Kanban(JIRA Agile)
innocarpe
0
130
Android TV at Google Developers Summit
innocarpe
0
72
경북대도서관 스마트앱 최종발표
innocarpe
0
170

Other Decks in Programming

See All in Programming
NSOutlineView何もわからん:( 前編 / I Don't Understand About NSOutlineView :( Pt. 1
usagimaru
0
290
CSC509 Lecture 11
javiergs
PRO
0
180
3rd party scriptでもReactを使いたい！ Preact + Reactのハイブリッド開発
righttouch
PRO
1
590
Identifying User Idenity
moro
6
9.6k
Why Jakarta EE Matters to Spring - and Vice Versa
ivargrimstad
0
660
みんなでプロポーザルを書いてみた
yuriko1211
0
200
macOS でできる リアルタイム動画像処理
biacco42
9
2.3k
Compose 1.7のTextFieldはPOBox Plusで日本語変換できない
tomoya0x00
0
170
役立つログに取り組もう
irof
28
9.4k
Generative AI Use Cases JP (略称:GenU)奮闘記
hideg
0
190
ActiveSupport::Notifications supporting instrumentation of Rails apps with OpenTelemetry
ymtdzzz
1
180
AI時代におけるSRE、
あるいはエンジニアの生存戦略
pyama86
4
1k

Featured

See All Featured
Keith and Marios Guide to Fast Websites
keithpitt
409
22k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
356
29k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
250
21k
Optimising Largest Contentful Paint
csswizardry
33
2.9k
How STYLIGHT went responsive
nonsquared
95
5.2k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
131
33k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
27
820
StorybookのUI Testing Handbookを読んだ
zakiyama
26
5.2k
Music & Morning Musume
bryan
46
6.2k
Unsuck your backbone
ammeep
668
57k
Why You Should Never Use an ORM
jnunemaker
PRO
54
9k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
15
2k

Transcript

  1. Tuist, بੑ਷ ೮חؘ Ӓېࢲ Modular Architecture ח যڌѱ ٜ݅য оաਃ?

    
 ӣ਋ࢿ - 29CM (Musinsa Inc.)

  2. Contents • Why Tuist? • Final Goal - µFeatures Architecture

    • Establishing the Foundation • Starting µFeatures-based development • Utilizing Feature App

  3. Why Tuist?

  4. None

  5. Why Tuist? • Simplified project configuration (w/ Swift) • Improved

    scalability for large projects • Enhanced collaboration among developers - Bene fi ts

  6. Simplified project configuration (w/ Swift)

  7. Improved scalability for large projects

  8. Enhanced collaboration among developers

  9. Final Goal - µFeatures Architecture https://docs.tuist.io/building-at-scale/microfeatures/

  10. None
  11. None
  12. None

  13. FeatureExample Feature FeatureTesting FeatureInterface FeatureTests

  14. FeatureExample Feature FeatureTesting FeatureInterface FeatureTests

  15. µFeatures Architecture Goals • Not aim for perfect architecture •

    Aim for appropriate architecture

  16. µFeatures Architecture Goals • Not aim for perfect architecture •

    Aim for appropriate architecture So what is appropriate?

  17. µFeatures Architecture Goals • Not aim for perfect architecture •

    Aim for appropriate architecture 1. Maximizing build caching
 2. Module-based development
 3. Well-extracted dependencies
  18. None

  19. Final products

  20. µFeatures

  21. Shared logics for µFeature

  22. Core logics for workspace

  23. Foundations / Third Parties

  24. None

  25. Establishing the Foundation

  26. None
  27. None
  28. None
  29. None
  30. None

  31. Needs to split interface / implement modules

  32. Needs to split interface / implement modules (especially Firebase..)

  33. None
  34. None
  35. None
  36. None
  37. None
  38. None
  39. None
  40. None
  41. None
  42. None

  43. Focus on appropriate architecture 1. Maximizing build caching
 2. Module-based

    development
 3. Well-extracted dependencies Again,

  44. Starting µFeatures-based development

  45. None
  46. None

  47. Abstract ViewController Factory

  48. None
  49. None
  50. None
  51. None
  52. None
  53. None
  54. None
  55. None
  56. None
  57. None
  58. None
  59. None

  60. One more thing, for µFeatures

  61. None

  62. Utilizing Feature App

  63. Utilizing Feature App 1. Rapid Feedback Cycle

  64. Utilizing Feature App 1. Rapid Feedback Cycle • make review

    and debugging faster

  65. Utilizing Feature App 1. Rapid Feedback Cycle • make review

    and debugging faster 2. Independent Development Environment

  66. Utilizing Feature App 1. Rapid Feedback Cycle • make review

    and debugging faster 2. Independent Development Environment • help focusing on the feature

  67. Utilizing Feature App 1. Rapid Feedback Cycle • make review

    and debugging faster 2. Independent Development Environment • help focusing on the feature 3. Concern - Dependency management in Feature App

  68. Utilizing Feature App 1. Rapid Feedback Cycle • make review

    and debugging faster 2. Independent Development Environment • help focusing on the feature 3. Concern - Dependency management in Feature App • requiring additional efforts to maintain
  69. None

  70. Summarize

  71. None
  72. None
  73. None

  74. Summarize • Design modularization milestone first • Focus on maximizing

    build caching • Aim for appropriate architecture • Build µFeatures architecture gradually

  75. Q & A

  76. Thank you! Wooseong Kim - 29CM [email protected]