Cloud-native is an evolving architecture. Existing vendors will keep on evolving their offerings and different teams inside your organization should be able to use the tool that will support them better in delivering their desired outcome fast. By implementing a standard application layer, you enable teams to adopt what works best for them while the DevOps team can focus on adopting the infrastructure components they believe to be best to support their organization.

I recently returned from a birthday trip to Napa Valley and got to spend some time with the Shipa Team in Palo Alto during the trip. Grabbing a coffee on my trek back to San Francisco, I overheard someone talking about YAML at the coffee shop and I had to hold back my laugh. You usually do not hear folks talking about YAML out in the public but this is San Francisco. For many engineers, YAML is a way of life.

Organizations rely more than ever on their engineering teams to get in front of their customers. Quickly delivering the latest functionalities to end-users in a reliable way can make or break a company these days. This need raises the pressure on engineering to deliver a scalable platform, rollout application updates faster, and manage applications efficiently once in production.

I guess at this point, you have heard of a company called Amazon and its business unit called Amazon Web Services, or AWS. Although you can read different stories about its beginning, one common thread across all of them is that it started with the need to scale quickly while enabling developers to deploy their services rapidly.

In this webinar, we talk with platform engineering leaders at BambooHR, a SaaS leader in the Human Resources space, about furthering their journey into Kubernetes. We are joined by Kelsey Hightower to help moderate and provide commentary on what he has seen in the space. As BambooHR kicks off their journey with Shipa, learn from the prospectus of the team moving the needle in engineering efficiency and developer experience.

Shipa Cloud is how we run the Shipa control plane on behalf of users in order to give them the fastest path possible to implementing Application as Code within their clusters. You can try out Shipa Cloud for free today by going to shipa.io. Besides being the fastest way possible to get started with Shipa, it also takes away the responsibility of upgrades, maintenance, and uptime of the control plane for our users, but that responsibility doesn’t just disappear.

Continuing on from Part One where we went through a brief history of containers and Kubernetes then Dockerized a NodeJS application, now we are ready to deploy to Kubernetes. If this is your first or nth time deploying to Kubernetes, Shipa makes this simple. You don’t have to worry about authoring multiple Kubernetes manifests and templates to deploy your application, all you need is an image.

Since its introduction in 2014 to the world, Kubernetes has been helping usher in the next generation of distributed workloads. As workloads started to be containerized, so did the need to manage the containers, thus the inception of container orchestrators. There have been a few container orchestrators out there before Kubernetes such as Docker Swarm and Apache Mesos. Though as a feature developer, Kubernetes can certainly feel like an 800-pound gorilla in the room.

For many of us in the technology world, around the holidays family will always ask you to solve their technology problems. Being in February, I am only several months away from sharing the below card with my family, again.

We are pleased to announce today that Shipa, the cloud-native Application as Code platform is now available on the AWS Marketplace. Bringing the power of Shipa to your internal customers on AWS infrastructure has never been easier with click to install from the AWS Marketplace.