After a long haitus, I return to continue this series. I’ve actually changed slightly what I’m doing with this blog, but the core remains the same but I’m utilizing one less external service. I have to preface this article again with my hosting of this blog is more about learning about these services on AWS. Even in the 5 month break between the first part and this part, AWS has come up with some great additions to their services.
I’ve been spending a lot of time re-evaluating my thinking of “cloud computing.” Today “cloud” is so diluted of a term, I hesitate to use it. Spinning up VPSes on the fly is a form of cloud computing, but I’m talking about some of the origins of it – Amazon Web Services for example. What’s the difference? A lot actually. I’m still learning as I go along, and this series of posts is meant to solve a couple of problems: Writing out my thoughts and trying to explain things will help me organize my own thoughts as I try to design the future infrastructure of my current business and potential future endeavors.
As the primary DBA at the company, I knew of a problem I wasn’t quite sure how to solve brewing. The short summary is that ever since the very first applications, we have been tracking statistics of app usage. Since we’ve been building apps for over 5 years now, it’s quite a massive data set. Infancy When I first started, I wanted to run as little software on the server as possible.
One of the posts I wrote last time I restarted this blog was a list of services or tools that I use that have aided me in running my business. Given that I wrote that a few years ago, I figured that an updated list would be in order. One stark change that has happened with me is that while I still dive in on iOS and Android code, my primary focus these days is on architectural and forward thinking things.