Decoding Modern Tech: Cloud, APIs, Wasm, Security, & More • Daniel Bryant & Matt Turner

Platform engineering and cloud native development require careful consideration of abstraction, security, and scalability, with API gateways, Wasm, and self-serve platforms playing key roles in efficient and secure application delivery.

Key takeaways
  • The need for abstraction and choosing which abstractions to expose is crucial in platform engineering.
  • The concept of “mechanical sympathy” is important, where developers need to understand the intricacies of how their code runs at a low level.
  • API gateways are becoming more versatile, going beyond just routing and protocol conversion to involve security, observability, and egress management.
  • Cloud native development requires careful consideration of egress management to prevent unauthorized access to systems.
  • Self-serve platforms should be locked down by default and have allow listing for specific services or applications to ensure security.
  • API gateways can be used to split cognitive load between developers and operations teams, allowing for more efficiency and scalability.
  • Wasm (WebAssembly) can be used to create high-performance, secure applications and can be executed on various platforms, including cloud, mobile, and edge devices.
  • Cloud native development involves a range of technologies, including Kubernetes, CNI, SDN, and service meshes, which can be complex to manage and require careful planning.
  • Security is a critical aspect of cloud native development, and developers need to be mindful of potential security risks and vulnerabilities.
  • The community is playing a crucial role in shaping the future of cloud native development, and events and conferences are important for knowledge sharing and collaboration.
  • The distinction between platform engineering and DevOps is becoming less clear, and teams are blurring the lines between the two disciplines.