Member-only story
The Move to Serverless… Digital Ocean, Heroku, AWS, OH MY!
I have vowed to try and write more about what I am doing in the technology space from day to day, but this is actually something that we have been experimenting with at 38th Street Studios going awhile back now and I’m just documenting it now. This idea is around the new craze and buzz surrounding “serverless computing”, “serverless architecture”, “the cloud”, etc.
Digital Ocean
For the longest time, we had always used Digital Ocean for droplets that we spun up and hosted everything from marketing websites to web apps on. It was great for learning, plus you had complete control over everything That was great, however, a downside was… you had complete control of everything…. For example, as some of the projects we made began to get more traffic and scale, our droplet was getting pounded by more traffic than it could reasonably handle, not to mention having to take the time to understand and debug items like nginx and firewalls. To scale, we set up a droplet to act as a load balancer and distribute the requests it received to other droplets that had replicas of the same code base on it, which all talked to a database that we had to have a failover and automatic mirroring on. At the end of the day, our bill was high, we were debugging dev ops, and doing everything except making progress coding.
