This week I continued working on the server architecture local implementation. I was able to get a working version of the multi-node data flow that can be redirected at different stages. I do this by having a specific node (in this case, the front end node) relay information to one of two back end/database nodes in order to begin a new data flow. In Node.js, it was even possible to have a fragmented video stream in which the data is sent in small chunks of about 1 MB that are relayed from database to web server to browser. There remains some debugging to do in the case of scrubbing (moving the current time instance to another).
In working on this locally deployed application, I noticed that for our intended architecture, there is exceedingly little additional functionality for our back end server tier when compared to our database tier. On that end, I observed that our intended virtual machine specification for the database nodes will likely the demands for both back-end and video storage functionality at once. Thus, I proposed to the group that we condense the back end and database server tiers into one comprehensive database access tier the idea was well liked. This change would streamline our server for greater speeds and reduced deployment costs.