PODCAST
Several themes and insights emerged from the conversation:
Platforms are evolving: While Kubernetes has emerged as a kind of standard, providing more granular control and enhancing the ability to curate different platform experiences for different types of teams, it isn't entirely accurate to say that the platform question is settled. Kubernetes may be the platform around which focus has converged because of its fluidity and flexibility, letting you do just about anything. But more broadly, platforms continue to evolve, in large part because there are so many different ways to accomplish the many tasks that make up cloud-native development. On one hand, more mature companies may be happy with the Kubernetes setup. Many others, though, want a more curated, structured and opinionated path, with tools sitting on top of Kubernetes.
PODCAST
Be sure to check out the additional episodes of the "Livin' on the Edge" podcast.
Key takeaways from the podcast included:
Creating a fast development loop is essential for engineering productivity. Sometimes engineers have to “bend the rules” in order to make this work for them.
PODCAST
Be sure to check out the additional episodes of the "Livin' on the Edge" podcast.
Key takeaways from the podcast included:
Creating an effective continuous delivery pipeline is essential for enabling fast feedback for developers.
PODCAST
Crystal Hirschorn, Director of Engineering - Infrastructure, SRE and Developer Experience at Snyk, shared some time with Ambassador Labs's Head of Developer Relations, Daniel Bryant, to talk about all things platform engineering and building control planes that “pave a path” for developers.
Here are some of the key takeaways from their conversation:
PODCAST
A number of key themes emerged:
HTTP/2 sped up HTTP/1 dramatically – but if you lose one packet on a connection, everything gets stalled until the packet is retransmitted.
This is a fundamental limitation of TCP, so HTTP/3 speeds up HTTP/2 even more by implementing the protocol on top of UDP.
PODCAST
Be sure to check out the additional episodes of the "Livin' on the Edge" podcast.
Key takeaways from the podcast included:
APIs must be designed as user interfaces in order to both provide the most value to end users, and be easy to consume by developers.
