Chapter 23. Cloud Processing Is Not About Speed
Rustem Feyzkhanov
Data and machine learning processing pipelines used to be about speed. Now we live in a world of public cloud technologies, where any company can procure additional resources in a matter of seconds. This fact changes our perspective on the way processing pipelines should be constructed.
In practice, we pay equally for providing 10 servers for 1 minute or 1 server for 10 minutes. Therefore, the focus shifts from optimizing execution time to optimizing scalability and parallelization.
Let’s imagine a perfect data processing pipeline: 1,000 jobs get processed in parallel on 1,000 nodes, and then the results are gathered together. This would mean that at any scale, the speed of processing doesn’t depend on the number of jobs and is always equal to the processing time for one job.
This doesn’t sound so impossible. Serverless infrastructure, which is becoming more and more popular, provides a way to launch thousands of processing nodes in parallel. In addition, more and more vendors now have pure container-as-a-service offerings, meaning that once you define, for example, a Docker image, it will be executed in parallel, and you will pay for only processing time. Not only that, but when serverless infrastructure and container as a service are coupled with native message buses or orchestrators ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access