Screencast Threadless: Serving Notifications Electives

  • Gregg Pollack
Badge student

Locked Content

A subscription is required for viewing this video. Enroll now to get full access to all Code School courses and content.

Enroll Now Sign in


  1. barrigaj said

    Is there a reason you would want a separate server for APIs? Why not have the same server that serves the http request also serve incoming API calls?

  2. bertomart said

    Scalability, maybe.

  3. Leonardo Graterol said


    Scalability and separation of concerns...

    The API handles all CRUD, notifications and business logic and is platform agnostic, it serves mobile apps, web apps and 3rd party apps.

    The web server handles the rendering of the app for web clients.

About This Screencast

In this episode of Feature Focus, Gregg Pollack and Carlos Souza walk you through how to implement a server with cross-origin request support for serving notifications like those on Threadless. They're joined by Nathan Hinshaw, lead front-end developer at Threadless, who provides feedback on their feature implementation.

Feature Focus is a screencast series focused on practical feature builds and development problem solving. Watch as we build out well-known site features in a simple way and then sit down with the original product developer to get feedback on our implementation.

You need to be an enrolled student in order to view this video and subscribe.

Enroll Now