A continuation of the Architecting Express series, this series will show you how to build an administrative web application to manage the public facing services. You’ll see how to integrate user authentication and authorization, how to build a proper reporting dashboard, and more!
The media service and analytics code are nearly feature complete at this point. However, the router for the media service is starting to get a little too large and ugly. There’s too much code and too many non-router-specific things happening in the router. In this episode, then, you’ll continue the path of keeping your router […]
After some much needed and highly successful code cleanup, it’s time to get back to the core analytics feature set for the media service. And wouldn’t it be nice to see where in the world downloads are happening? Or operating system, browser and other bits of info about the downloaders? In this episode, you’ll learn about […]
The code for the analytics service is working now, and errors are being reported appropriately. Things seem to be going well for the media service! But there’s something not quite right about the code in the analytics background process. It’s a bit too cluttered, it seems. It has too many things going on in a […]
In the previous episode, the Keen.io code for the analytics service was moved into a separate process using RabbitMQ. Toward the end of the episode, however, there were a number of issues that we ran into – most notably was an error in syntax not being reported correctly. In this episode, you’ll see the root […]
In the last episode, you saw the basics of getting Keen.io up and running to track downloads for the media service. In spite of the success in getting it to work, there’s some potential drawbacks to having this solution hard coded into your router. What happens if Keen.io goes down or you have a network […]