This brings us to the end of this chapter. A lot of what we did in this chapter was already familiar to you from previous applications, but there were a few nuggets that you shouldn't ignore. The main aspect is the strong server component. It is easy to forget that a Backbone application will always have the server code behind it, and often that code will be much more than a main template being rendered and a bunch of routes that shuttle JSON back and forth. There's often significant logic, data handling, and other details that will be taken care of on the server. As we saw, it's often possible to perform this logic on either the client or the server—we could have captured the RSS feed and processed it in either position. When building your own applications, it's important to make good decisions about where processes take place. It's often much quicker to do something on the client (no request/response to wait for), but you'll probably have more power and ability on the server, so...