A Node.JS Holiday Season Articles
-
Introducing AWSBOX, the DiY PaaS for Node.JS – A Node.js holiday season, part 12
This is episode 12, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. It’s the last part, and covers awsbox. Once you’ve written a server in Node.js, how do you deploy it? Instead of using a pre-existing “Platform as a Service” (PaaS) provider, the Identity team at Mozilla […]
-
Localization in Action, part 3 of 3 – A Node.js holiday season, part 11
This is episode 11, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. It’s the last part about localization, hopefully making you feel all ready to handle that now! Using Our Strings So first we added the i18n-abide module to our code, then our Localization (L10n) team did […]
-
Localization community, tools & process, part 2 of 3 – A Node.js holiday season, part 10
This is episode 10, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. Let’s talk some more localization! In our previous post “How to Localize Your Node.js service”, we learned how to add i18n-abide to our code. We wrapped strings in both templates and JavaScript files. As developers, […]
-
Localize Your Node.js Service, part 1 of 3 – A Node.js holiday season, part 9
This is episode 9, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. Now it’s time to delve into localization! Did you know that Mozilla’s products and services are localized into into as many as 90 languages? The following are just a few examples of localization: Text translated […]
-
Fantastic front end performance, part 3 – Big performance wins by optimizing fonts – A Node.js holiday season, part 8
This is episode 8, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. Today we’re talking even more front end performance! We reduced Persona’s font footprint 85%, from 300 KB to 45 KB, using font subsetting. This post outlines exactly how we implemented these performance improvements, and gives […]
-
Taming Configurations with node-convict – A Node.JS Holiday Season, part 7
This is episode 7, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. Today it’s time to talk about configuration. In this installment of “A Node.JS Holiday Season” series we’ll take a look at node-convict, a tool that helps manage the configuration of node.js applications. It provides transparent […]
-
Fantastic front-end performance, part 2: caching dynamic content with etagify – A Node.JS Holiday Season, part 6
This is episode 6, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. Today it’s time for the second part about front end performance. You might know that Connect puts ETags on static content, but not dynamic content. Unfortunately, if you dynamically generate i18n versions of static pages, […]
-
Building A Node.JS Server That Won't Melt – A Node.JS Holiday Season, part 5
This is episode 5, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. For this post, we bring the discussion back to scaling Node.JS applications. How can you build a Node.JS application that keeps running, even under impossible load? This post presents a technique and a library that […]
-
Fantastic front-end performance Part 1 – Concatenate, Compress & Cache – A Node.JS Holiday Season, part 4
This is episode 4, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. It’s the first post about how to achieve better front-end performance. In this part of our “A Node.JS Holiday Season” series we’ll talk about front-end performance and introduce you to tools we’ve built and use […]
-
Using secure client-side sessions to build simple and scalable Node.JS applications – A Node.JS Holiday Season, part 3
This is episode 3, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. It covers using sessions for scalable Node.js applications. Static websites are easy to scale. You can cache the heck out of them and you don’t have state to propagate between the various servers that deliver […]
