Serverless Spring - Nate Schutta 2/2
0 likes185 views
The document discusses serverless computing and container technologies like Functions as a Service (FaaS) and Kubernetes. It explains that these technologies provide various levels of abstraction away from physical servers, allowing developers to focus on code rather than infrastructure. Project riff is highlighted as a new FaaS platform for Kubernetes that provides an agnostic layer for building and deploying serverless workloads on-premise or in the cloud using containers.
Serverless Spring - Nate Schutta 2/2
- 1. Life moves pretty fast…
- 2. From IaaS to CaaS to PaaS…
- 3. First things first. There are still servers.
- 4. We are just (further) abstracted away from them.
- 5. We don’t have to spend time provisioning, updating, scaling…
- 6. In other words it is someone else’s problem.
- 9. IaaS Containers Container Container Scheduling Primitives for Networking, Routing, Logs and Metrics Platform Application Container Images L7 Network Logs, Metrics, Monitoring Services Marketplace Team, Quotas & Usage Container Serverless Function Function Execution Function Scaling Event Stream Bindings Container Developer Provided Tool Provided
- 10. Different levels of abstraction.
- 11. Hardware IaaS Containers Platforms Serverless More Flexibility Fewer Standards Lower Complexity Operational Efficiency Push as many workloads up the stack as feasible.
- 12. Some argue it is the new PaaS. http://redmonk.com/sogrady/2018/01/26/serverless-is-the-new-paas/
- 13. Veritable plethora of options.
- 14. AWS Lambda, Azure Functions, Google Cloud Functions…
- 15. Knative, riff, OpenWhisk, Kubeless, Fission…
- 16. Definitely suffers from the shiny new thing curse.
- 18. And everything that entails.
- 20. Fair to say FaaS is a subset of serverless.
- 21. Though many use the terms interchangeably.
- 22. There *are* very good reasons to utilize this approach!
- 23. Some relate specifically to a platform.
- 24. Perhaps you already have data with a provider.
- 25. Using Amazon S3 for example.
- 26. You might want to tap into particular services offered by a provider.
- 27. Perhaps you want to utilize Google Cloud Machine Learning Engine.
- 28. But it isn’t just a new a way to cloud.
- 29. There are serious efficiency gains to be had with this approach!
- 31. Functions push us further up the abstraction curve.
- 32. Allows us to focus on implementation not infrastructure.
- 33. Do you know what OS your application is running on?
- 34. Do you care?
- 35. What *should* you care about?
- 36. Where is the “value line” for you?
- 37. We want to get out of the business of “undifferentiated heavy lifting”.
- 38. Focus on business problems, not plumbing problems.
- 40. Function hasn’t been called recently?
- 42. Request comes in? Instance springs into existence.
- 43. First million (or two) requests are free*.
- 44. * Additional fees may apply.
- 45. For example: data transfer fees or other services you leverage.
- 46. Functions aren’t free however.
- 47. Past the free tier, you’re charged a fractional amount there after.
- 48. Charged based on number of requests, run duration and resource allocation.
- 49. Can be challenging to determine just how much it will cost…
- 50. But for certain workloads, it is very cost effective.
- 52. Serverless ops?
- 53. Again, less for us to worry about.
- 54. Rely on a platform.
- 55. What use cases fit well with functions?
- 58. Infrequent (or sporadic) requests.
- 62. IoT, machine learning, log ingestion, batch processing, stream processing.
- 63. “Conversational UIs” aka digital assistants like Alexa.
- 64. CI/CD automation, chat integration.
- 65. Website back end services such as logging, post handlers, authentication.
- 66. Event processing, monitoring, notifications, alerting, security scanning.
- 68. It isn’t a good fit for every workload.
- 70. But you knew that.
- 72. riff is for functions. https://projectriff.io
- 74. Built on top of Knative.
- 75. Built on the experience of Spring Cloud Streams and Data Flow.
- 76. Functions can be polyglot.
- 77. Scale up and down as needed.
- 78. ICE - CAP for serverless.
- 80. Pick two.
- 81. What are your concerns? Resource utilization? Immutable containers?
- 83. If we keep containers running, we’re paying for idle resources.
- 84. If we inject code into a container, we lose immutability.
- 85. If we launch containers on demand, we have slow startup experience.
- 87. 🤔
- 88. Many platforms use dynamic loading.
- 89. But the goal with riff is to give *you* control over the tradeoffs.
- 90. riff is thin.
- 91. Functions are deployed and run as Knative Services.
- 92. CLI builds on Knative and kubectl.
- 93. Can create function from source.
- 94. Or from a repo.
- 95. Push image to DockerHub or GCR.
- 96. Rebuilding triggers a new Knative Revision for each build.
- 97. Subscriptions have their own CLI.
- 99. Very new, evolving rapidly.
- 100. Agnostic layer for FaaS. Run it on premise or public cloud.
- 101. riff under the hood.
- 103. Lot of fragmentation in the functions space…
- 104. “Kubernetes-based platform to build, deploy, and manage modern serverless workloads.”
- 105. “Kubernetes-native APIs for deploying serverless-style functions, applications, and containers.” https://projectriff.io/blog/announcing-riff-0-1-0-on-Knative/
- 106. Middleware.
- 107. Run anywhere.
- 108. Orchestrating, routing and traffic management.
- 109. Scale up, scale down to zero.
- 110. Essentially agnostic layer for FaaS.
- 111. Built on Kubernetes and Istio.
- 112. Provides three major building blocks.
- 113. Build - pluggable model for building containers from source.
- 114. Designed to be part of a CI/CD pipeline.
- 115. Supports multiple build methods.
- 116. Kaniko, buildpacks, Dockerfiles, Bazel.
- 117. Four main elements to a build…
- 118. Where is the source code?
- 119. Steps or templates - the actual work to build the container.
- 120. Service account that will run the build.
- 121. Volumes - available during the build steps.
- 122. Eventing - publish/subscribe to event streams like Kafka.
- 123. Abstraction over the event stream.
- 124. Don’t worry about the underlying messaging platform.
- 125. Leverages Kubernetes custom resources.
- 126. Channels aka topics.
- 127. Bus - the provider aka Google Cloud PubSub, Apache Kafka, RabbitMQ…
- 129. Serving - scale up or down to zero.
- 130. Scale up in response to lag, scale down when demand slows.
- 131. Scale to zero when appropriate.
- 132. Also provides revision control.
- 133. Istio routes traffic to versions of functions (aka revisions).
- 134. Facilitates zero downtime deploys, blue-green, etc.
- 137. Which approach should *you* choose?
- 139. There is no one right answer here.
- 140. && ! ||
- 141. Not all workloads fit in each bucket.
- 142. There are tradeoffs!
- 143. But you knew that.
- 144. — Uncle Ben “With great power comes great responsibility.”
- 146. Do you want developers thinking about OS patches?
- 147. Or just pushing apps?
- 149. How many operators does it take to manage a bespoke environment?
- 152. They are designed to protect you.
- 153. How do you want to allocate *your* resources?
- 154. Choose the option that fits the problem.
- 158. Push as many workloads as you can up the abstraction hierarchy.
- 159. Evolving space.
- 160. Life Functions move pretty fast…
- 161. riff is *really* new.
- 162. Want more?
- 163. Riffing on Project riff. https://soundcloud.com/pivotal-insights/riffing-on-project-riff-ep-56
- 165. riff is for functions. https://www.youtube.com/watch? v=mlRSp9Z3zwY&list=PLAdzTan_eSPQ2uPeB0bByiIUMLVAhrPHL&index=14
- 166. Dave Syer - cloud abstractions, functions, containers, apps. https://www.youtube.com/watch?v=icZaMdNExNU
- 167. Knative and riff for Spring Developers. https://www.youtube.com/watch?v=zCObFAhrhJM
- 168. Knative, riff, and Pivotal Function Service. https://www.youtube.com/watch?time_continue=166&v=_OiGt4QwdlM
- 169. Good luck!
- 170. Nathaniel T. Schutta @ntschutta ntschutta.io Thanks! I’m a Software Architect, Now What? with Nate Shutta Modeling for Software Architects with Nate Shutta Presentation Patterns with Neal Ford & Nate Schutta