This is the last part in a series of three showing how to build a simple JavaScript architecture.

After seeing how to create a NodeJS application to track tweets and send them to a Google Chrome Extension in real time, we are going to see how to store and query them using a MongoDB database.

For a better understanding, this post starts by explaining the basics of MongoDB and then deals with its integration in a NodeJS application.

This post is the first of a three-part series showing how to build a complete javascript architecture using :

• NodeJS : For the server side. We will use Socket.IO to manage long-terms real-time connection.

• Google Chrome Extension : For the client side. WebSocket, Notification and Local Storage will be used.

• MongoDB : To store the datas.

To illustrate our architecture we are going to create a Node application that will track tweets about the “What’s Next” event and broadcast them in real time to the clients. The client will be a Google Chrome browser extension and will use two features of the HTML5 specification to display the tweets broadcasted by the server. In the last post I will introduce the MongoDB database, we will use it to store tweets and provide some statistics when the event ends.