Photos
Videos
KubeCon Pancakes Day 2: Which Comes First, Kubernetes or the Service Mesh?
Image
2
KubeCon Day 1 Pancakes: Shifting Cloud Native Security All the Way Left
Image
2
The Reemergence of Events-First Approaches.
Image
1
Posts

The ideal state of a cloud native shop is to run a development and deployment pipeline that can seamlessly move applications from the developer’s laptop to the data center (or the edge) without any manual intervention. And while there are many tools available to facilitate such automation — Helm, Operators, CI/CD toolchains, GitOps architectures, Infrastructure-as-Code tools such as Terraform — all too often edge cases and exceptions still require personal attention, bringing... DevOps pipelines to a halt.

The missing pieces of the puzzles are a control plane and a unified application model for the control plane to run upon, asserted Phil Prasek, a principal product manager at Upbound, in this latest episode of The New Stack Context podcast. Prasek envisions a time when organizations can build their own customized set of platform services, where developers can draw from a self-serve portal the building blocks they need — be they containerized applications or third-party cloud services, and have the resulting app run uniformly in multiple environments.

See More

Back in 2018, when AWS AppSync became available to the world, I wrote a series of blogs detailing what the Amazon Web Services’ service meant for GraphQL development.

The first post was titled The Comforts of GraphQL with AWS AppSync and I made the case for the development of GraphQL applications using the AWS service. In the later posts, I talked about serverless GraphQL with AWS lambda functions via AWS AppSync and the need for monitoring your serverless GraphQL applications.

Since 2018, there have been various developments to the AWS AppSync service that further augment the GraphQL development experience. It is these developments that I will focus on in this post.