book

Programming JavaScript Applications

by Eric Elliott

June 2014

Intermediate to advanced

254 pages

6h 2m

English

O'Reilly Media, Inc.

Read now

Unlock full access

IntroductionWho This Book Is ForWho This Book Is Not ForUnit TestingConventions Used in This BookSafari® Books OnlineHow to Contact UsThanks
Advantages of JavaScriptPerformanceObjectsSyntaxFirst-Class FunctionsEventsReusabilityThe Net ResultAnatomy of a Typical Modern JavaScript AppInfrastructureJSON: Data Storage and CommunicationNoSQL Data StoresRESTful JSON Web Services
Minimize Side EffectsFunction DefinitionNamed Function ExpressionsLambdasImmediately Invoked Function ExpressionsMethod ContextFunction.prototype.bind()Function ScopeHoistingClosuresMethod DesignNamed ParametersFunction PolymorphismMethod dispatchGenerics and Collection PolymorphismMethod Chaining and Fluent APIsFunctional ProgrammingStateless Functions (aka Pure Functions)Partial Application and CurryingAsynchronous OperationsCallbacksPromises and DeferredsConclusion
Classical Inheritance Is ObsoleteFluent-Style JavaScriptPrototypesDelegate PrototypesPrototype CloningThe Flyweight PatternObject CreationFactoriesPrototypal Inheritance with StampsConclusion
Principles of ModularityInterfacesThe Module PatternAsynchronous Module DefinitionPlug-InsNode-Style ModulesnpmES6 ModulesBuilding Client-Side Code with CommonJS, npm, Grunt, and BrowserifyDefining the AppFeature ImplementationBundling and DeploymentConclusion
Client-Side ConcernsModule ManagementGetting startedRegistration, loading, and renderingEventsEvent emittersEvent aggregatorsQueues and stacksChoosing the right event modelEvents by exampleModel View Controller/MV*Presentation and DOM ManipulationView eventsEvent delegationTemplatesWeb ComponentsServer-Side ConcernsGetting Started with Node and ExpressInstalling Node and ExpressOrganizing files in NodeNode librariesConfigurationExpressCreate your appRoutingMiddlewareLet it crashTemplatesNext stepsConclusion
AuthenticationPasswordsRainbow tablesPassword saltsBrute forceVariable time equalityStolen passwordsCredentialMultifactor AuthenticationKnowledge factorPossession factorInherence factorFederated and Delegated AuthenticationMozilla PersonaWebIDDelegated authenticationAuthorizationAuthorizing ApplicationsOAuth 2.0Conclusion
DebuggingServer OperationsSecurityAuditingBusiness AnalyticsViral FactorLogging ChecklistLogging RequestsLogging ErrorsSample Log OutputLogging Service AlertsLogging GoalsProfiling and InstrumentationLogging Client-Side EventsDeciphering DataConclusion
UsableFocusConsistencyUse common conventionsResourceful routingSelf-Describing: HypermediaAffordancesHATEOASHTML as an API Media TypeJadeJironResponsive APIsOptimizing for SpeedConclusion

Organizing FeaturesScale of a FeatureFeature GroupsLifespan of a FeatureDevelopmentStagingProduction TestingFeature RolloutDefault ActivationFull IntegrationImplementationConclusion
Conclusion
Example TestsQUnit PrimerCode QualityBest Practices Quick ReferenceIndentation: Be ConsistentUse SemicolonsBracket Placement: Right SideAvoid Name CollisionsAlways Use varUse One var Statement per FunctionAvoid Constant AbuseUse Functional Iterators When PossibleBe Careful with if StatementsAvoid Side EffectsDon’t Use switchDon’t Use eval()

Content preview from Programming JavaScript Applications

Chapter 9. Feature Toggle

Continuous deployment is the process of testing, integrating, and deploying software in rapid cycles in order to deliver bug fixes and new features to customers as quickly as possible. It gained popular acceptance as a cornerstone of extreme programming and agile development and is very popular among Software as a Service providers.

A feature toggle system allows you to integrate features into your codebase even before they’re finished and ready to release. During development, the features are toggled off by default. In order to turn them on, you must enable them manually. Using this method, you can deploy unfinished or untested changes into your production system without interfering with the user experience.

Feature toggles can allow software integration cycles that run in weeks, days, or even hours, as opposed to months or years. They are an essential component in a broader continuous integration system.

Feature toggles are popular in the startup community but have gained widespread acceptance in the enterprise, including larger companies such as Facebook, Google, Yahoo, and Adobe.

Organizing Features

Deciding how to organize features begins with deciding what exactly constitutes a feature. Once you figure that out, you should also decide how you’re going to classify or group features together.

Scale of a Feature

“Feature” can mean almost anything, ranging from a new page or route to an additional option on a select element. Deciding how to classify the scope ...