Continuous Integration (CI), Continuous Delivery (CD) and Continuous Deployment (CD) are three processes that automate integrating software development into a product and deploying the modified product to test and production environments.
When we were building out our first UI at Speedscale we wanted to get something up and running quickly. Fortunately there are a ton of options of web frameworks that can be used to throw together a quick “hello world” kind of application. However, a SaaS application needs a lot more than just displaying data. It needs to handle user authentication, loading data from a backend API, displaying data in a variety of formats, etc.
Running your own Kafka is starting to feel like wading through oatmeal. We’re not the only ones thinking that. The majority of organizations we speak to have or are in the process of moving their Kafka to a managed service. If you’re already an AWS-shop, Managed Streaming for Apache Kafka (MSK) is a no-brainer. It is the same Kafka that we know and love and integrated with other AWS services such as IAM, Cloudwatch, Cloudtrail, KMS, VPC and more.
Kong Enterprise is a service connectivity platform that provides technology teams with the architectural freedom to build, operate, observe, and secure APIs and services anywhere. From Kong’s inception, we’ve been aligned with Amazon Web Services (AWS), enabling our customers to quickly and efficiently deploy Kong on their AWS accounts. As companies move from monolithic to microservice applications and beyond, Kong helps teams manage this transition.
Infrastructure as code has been an important practice of DevOps for years. Anyone running an Apache Kafka data infrastructure and running on Kubernetes, the chances are you’ve probably nailed defining your infrastructure this way. If you’re running on Kubernetes, you’re likely using operators as part of your CI/CD toolchain to automate your deployments.
