4. Component Communication and Responsibilities | JavaScript at Scale

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

JavaScript at Scale

By : Adam Boduch

4.5 (2)

JavaScript at Scale

4.5 (2)

By: Adam Boduch

Overview of this book

Have you ever come up against an application that felt like it was built on sand? Maybe you've been tasked with creating an application that needs to last longer than a year before a complete re-write? If so, JavaScript at Scale is your missing documentation for maintaining scalable architectures. There's no prerequisite framework knowledge required for this book, however, most concepts presented throughout are adaptations of components found in frameworks such as Backbone, AngularJS, or Ember. All code examples are presented using ECMAScript 6 syntax, to make sure your applications are ready for next generation browsers.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Scale from a JavaScript Perspective

1. Scale from a JavaScript Perspective

Scaling influencers

Architectural perspectives

The browser is a unique environment

Making architectural trade-offs

Frameworks versus libraries

Summary

2. Influencers of Scale

2. Influencers of Scale

Scaling users

Scaling features

Scaling development

Influencer checklist

Summary

3. Component Composition

3. Component Composition

Generic component types

Extending generic components

Mapping features to components

Decomposing components

Pluggable business logic

Organizing component code

Summary

4. Component Communication and Responsibilities

4. Component Communication and Responsibilities

Communication models

Communication data schema

Traceable component communication

Communication overhead

Areas of communication responsibility

Loosely-coupled communication

Component layers

Summary

5. Addressability and Navigation

5. Addressability and Navigation

Approaches to routing

How routers work

URI parts and patterns

Mapping resources to URIs

Triggering routes

Router configuration

Troubleshooting routers

Summary

6. User Preferences and Defaults

6. User Preferences and Defaults

Preference types

Supporting locales

Setting the locale

Generic component configuration

Configuring behavior

Changing the look and feel

Performance implications

Summary

7. Load Time and Responsiveness

7. Load Time and Responsiveness

Component artifacts

Loading components

Communication bottlenecks

Component optimization

API data

Optimizing components at runtime

Summary

8. Portability and Testing

8. Portability and Testing

Decoupling the backend

Feature design process

Unit testing tools

Testing mock scenarios

End-to-end tests and continuous integration

Summary

9. Scaling Down

9. Scaling Down

Scaling constraints

Conflicting features

Design failures

Application composition

Summary

10. Coping with Failure

10. Coping with Failure

Failing fast

Fault tolerance

Failure recovery

Performance and complexity

Logging and debugging

Improving the architecture

Summary

Index

Index

Customer Reviews

4.5 (2)

5 star

50%

4 star

50%

3 star

0%

2 star

0%

1 star

0%

Communication overhead

One advantage of directly invoking a method on a component is that there's very little overhead involved. When all inter-component communication is brokered through an event triggering mechanism, there's no way to escape at least a little overhead. In fact, overhead associated with this indirection is hardly noticeable; it's other overhead factors that can cause scalability issues.

In this section we'll look at event triggering frequency, callback execution, and callback complexity. Each of these has the potential to degrade the performance of our software to the point where it is unusable.

Event frequency

When our software has only a handful of components, there's a fundamental limit on the frequency of events. Where event frequency can quickly turn into a problem is when there are lots of components, some of which trigger events in response to events. This means that if the user is doing something quickly and efficiently, or if there are several Ajax responses arriving...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

JavaScript at Scale

Search

Your notes and bookmarks