CST 438 - Week 6

This week we learned about Compute as a Service (CaaS), where compute is shorthand for the computing power needed to run programs. The chapter we read provided an overview on what this entails. In the early 2000s, running code on computers was generally a slow process. Engineers would use tools like SFTP in order to upload their programs and then connect to each machine using SSH. This worked at a smaller scale, however as companies like Google grew, it became a problem. If something went wrong, engineers would have to manually check each machine and restart program. As a result of this, companies began using automation - scripts and monitoring tools were created to help deploy code, see if it was running correctly, and to restart it if it failed. As time passed smarter systems were build that provided additional improvements. These improvements led to what he now call "Compute as a Service" (Caas), where computers automatically handle most of the work.