I’ve had a nice amount of exposure to the Golang language when I first started playing around with docker and its environment. At one time I actually had to go through the docker source code and the accompanying kernel source code for namespaces, cgroups and some other stuff. I had done some simple code execution and modifications but not a large scale system design.
Let’s start with a simple tic tac toe game that I forked. https://codepen.io/dovidkopel-the-bold/pen/zLvWbz. This is the original repository.
This is a novel approach to a database design that is sorely needed. Evolution in data storage has been significant but in many ways fairly the same general approach. Flat files was one of the first ways data was stored. A database was the next evolution. Being able to take advantage of indexing data providing a means to quickly access data without having to seek through its entirety. The purpose of this article is not to take a tour through the history of the database, but please bare with me I assure you its worth its while. There was a time when the DBA was the all powerful ruler of the database and analysts as well as engineers had little control over the schema and the data at all. One major issue when dealing with big data is handling data locality. There are two different types of databases that are often mutually exclusive: OLTP (Online Transaction Processing) and OLAP (Online Analytical Processing).
Over my career I’ve participated in probably over a hundred interviews. No matter what the position these are the four things I really look for. A resume is a piece of paper, I can usually gauge in five minutes if the candidate has what is needed for the given role.