MTGStocks 2.0 release
This is the first news post done through the new MTGStocks version! Before we get into the new version, I want to back up a little and highlight when this all began. I used to play Magic in high school and I still remember that I used to buy
Tempest boosters, because I wanted more Slivers. Unfortunately, at some point, I stopped playing around Invasion. Luckily in college, I met people who played, of which some of them ended up as some of my closest friends. Also, I started going to drafts when Lorwyn come out, still one of my favourite sets. This renewed addiction also sparked my interest in the finance market, since I wanted (*needed!!*) new cards and had to do it on a budget. Especially since we were mostly interested in the Legacy format. *\*yikes\**
I believe MTGStocks started around March 2012. I wanted to index the prices and do some statistics around these prices. Around that time I was toying around a lot in PHP, because why the hell not? PHP was amazing for tinkering with stuff, since it was easy to do, easy to understand and is quite intuitive. I barely had any knowledge about development stacks, frontend, backend or any of that stuff, so it was all mashed together in one giant application. At this stage, the project was never meant for anyone else other than myself and my friends and was simply called “Magic index prices”. I ran it somewhere in a subfolder of a domain I owned. In September, I got tired of using the long URL all the time and I came up with a name and registered the domain: mtgstocks.com.
People over at Quiet Speculation somehow got wind of this domain, and started using it. This led me to re-do everything in Ruby on Rails, since the code I created simply couldn’t handle the traffic. This implementation had been active for years and is what most of you are familiar with. Like most developers, I tend to be very lazy, so I spent a lot of time automating tasks for MTGStocks. This worked out pretty well, making sure it could run without too much attention. However, traffic kept increasing and data started to add up. As several people noticed, the site became sluggish.
Nowadays, I work as a frontend developer and realised that the current implementation couldn’t stay. All logic was being performed by the server and it simply couldn’t keep up anymore. I set myself a goal. I wanted to redo everything, but this time with an actual development stack. Not only that, I wanted to learn something new and extend my own knowledge. I decided I would still use Ruby on Rails for the backend, but I wanted a separate frontend, and ended up using Angular4.
This is the result of my work. I rebuilt everything from scratch, restructured the database structure and prepared it for future updates I have in mind. Automated even more than I used to, so I can do more with the same time available. It's definitely not finished yet, so keep your eye out for new functionalities. So if you find any bugs or if you really think we all could benefit from a feature, please let me know! Your input has always been greatly appreciated!