Server side coding options - AJAX and the graphing calculator - Part 4 in a series
The What and Why of Server Side Scripting
In the previous hubs in this series, I introduced how to retrieve data from a Web server using AJAX, and a simple application for charting personal geographies. In order to take this application further, I will need to start developing code on the server side. Basically, fetching already prepared data files from a server, is not very flexible and limits how feature rich the application can be. Using code running on the server to prepare custom data in response to a request opens up many more possibilities.
Let's call the application that I want to develop Geo-match, users will log their daily travels into the application. In return for this effort, they will be able to chart how their daily routes compare with geo-friends and maybe find some new people to meet or new places to go.
I will also pick one other mechanism that will be helpful in developing Geo-match; a database. There are many options here, as well. I could construct my own database out of plain files. I could use some No-SQL option, such as, Cassandra. Or, I could use a traditional, relational database. I will pick MySQL, because it is a common choice, it will meet the immediate needs of Geo-match, I don't have to pay anything to use it, and it is convenient for me.
In order to implement Geo-match, I will have users enter route entries that contain places they visited: who? where? when?
In my next Hub on this topic, I will start laying code. In this Hub, I just wanted to motivate why server side code is useful and cover some of the choices of technology that is available to use.