Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Large Scale JavaScript Application Architecture
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Frontend NE
February 04, 2016
Technology
1
780
Large Scale JavaScript Application Architecture
Frontend NE
February 04, 2016
Tweet
Share
More Decks by Frontend NE
See All by Frontend NE
Standardizing 'select': What the future holds for HTML - Stephanie Stimac @ FrontendNE
frontendne
4
410
CSS Regression testing - James A Lambert @ FrontendNE
frontendne
1
340
Building a design system for Lloyds Banking - Lilly Dart @ FrontendNE
frontendne
0
1.5k
What I learnt about hiring diverse teams from conducting a fully-anonymous recruitment process - Bethan Vicent
frontendne
0
290
Web Design that Doesn't Make Trans People Uncomfortable - Jessica Kelsall
frontendne
0
750
Contain yourself - Docker for developers
frontendne
2
270
Design process of a website
frontendne
0
320
What the JAMstack?
frontendne
1
940
Talking the talk
frontendne
0
510
Other Decks in Technology
See All in Technology
ZOZOにおけるAI活用の現在 ~開発組織全体での取り組みと試行錯誤~
zozotech
PRO
5
4.8k
15 years with Rails and DDD (AI Edition)
andrzejkrzywda
0
170
会社紹介資料 / Sansan Company Profile
sansan33
PRO
15
400k
オープンウェイトのLLMリランカーを契約書で評価する / searchtechjp
sansan_randd
3
650
Introduction to Sansan, inc / Sansan Global Development Center, Inc.
sansan33
PRO
0
3k
What happened to RubyGems and what can we learn?
mikemcquaid
0
250
~Everything as Codeを諦めない~ 後からCDK
mu7889yoon
3
270
Sansan Engineering Unit 紹介資料
sansan33
PRO
1
3.8k
Meshy Proプラン課金した
henjin0
0
250
Context Engineeringの取り組み
nutslove
0
280
セキュリティについて学ぶ会 / 2026 01 25 Takamatsu WordPress Meetup
rocketmartue
1
290
AIと新時代を切り拓く。これからのSREとメルカリIBISの挑戦
0gm
0
760
Featured
See All Featured
Prompt Engineering for Job Search
mfonobong
0
160
For a Future-Friendly Web
brad_frost
182
10k
Reflections from 52 weeks, 52 projects
jeffersonlam
356
21k
The Limits of Empathy - UXLibs8
cassininazir
1
210
Rebuilding a faster, lazier Slack
samanthasiow
85
9.4k
Into the Great Unknown - MozCon
thekraken
40
2.2k
Agile that works and the tools we love
rasmusluckow
331
21k
Color Theory Basics | Prateek | Gurzu
gurzu
0
190
KATA
mclloyd
PRO
34
15k
Paper Plane (Part 1)
katiecoart
PRO
0
4k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
1
290
The Curious Case for Waylosing
cassininazir
0
230
Transcript
Large Scale JavaScript Large Scale JavaScript Application Architecture Application Architecture
ahumphreys87 ahumphreys87 JavaScript Architect at Bede Gaming. JavaScript Game Framework
that powers cross platform Bingo client and Slots games. Node.js Slots Engine, Chat Server. Node.js API facade. Core contributor to Marionette.js Issue triaging, Pull Request reviews. Bug fixing. New features!
Introduction Introduction What is a large JavaScript application? Common Pitfalls.
Useful Patterns. How frameworks apply these principles. Questions???
Over 100,000 LOC? Over Xmb in size? Lots of files?
Hard to maintain What is a Large JavaScript What is a Large JavaScript Application? Application?
"A large JavaScript application is a non-trivial application that requires
significant effort to maintain and where most of the data manipulation takes place in the browser." Addy Osmani
Modularise Modularise Break the large application up. Think of logical
components. Different sections on the screen?
4 Questions 4 Questions 1. Can I reuse my modules?
2. Will my application still function if this breaks? 3. Is it testable? 4. Does it depend on anything else?
Common Pitfalls Common Pitfalls Tight coupling. Event webs. Lack of
tests.
Tight Coupling Tight Coupling Modules depend on each other. What
happens if another module breaks? Can we reuse this module? Can you test it?
Event Webs Event Webs
Often caused by tight coupling. Modules fire events between each
other. Debugging becomes difficult. Untestable.
Loosen up! Loosen up! Loosely coupled modules. They can be
reused. They don't depend on others. They are easy to test. Create a Facade. Create a Mediator.
Facade Facade
Abstracts complexity. Exposes a simple interface. bind/trigger. Modules only communicate
with the facade.
Mediator Mediator
The "brains" of the application. Performs application specific actions based
on the events. Controls what the facade listens for. Controls what the facade sends where.
The Result The Result Modules can break without breaking the
full application. Modules can be tested independently. Modules can be reused.
How do the big guns do it? How do the
big guns do it? Backbone.Radio Services Vanilla Classes Directives Services 2 way data binding Flux Action / Dispatcher Components Components. Actions Routes / Controllers
Questions??? Questions???