Nate Lee here, and I’m one of the founders of Speedscale. The founding team’s worked at several observability and testing companies like New Relic, Observe Inc, and iTKO over the last decade. Speedscale traffic replay was borne out of a frustration from reacting to problems (even if they were minor) that could have been prevented with better testing.
Kubernetes shouldn’t be reserved for production. Using local Kubernetes in development means you can build and test your service using the same technologies as your live deployments. Some organizations provide a shared Kubernetes cluster for development activities. Others offer on-demand virtual clusters that serve staging environments for significant changes.
It's impossible to learn about containerization without hearing about Docker and Kubernetes. These two tools together dominate the world of containers, both being the de-facto standard in what they each do. When you're first getting started learning about containers, it can be quite a challenge to figure out what the differences are between these two tools.
Mocking APIs is an increasingly popular trend, with more and more developers seeing the advantages of mocking dependencies rather than spinning up actual duplicates of resources. On a high-level, a mock API means that you have a service that returns static data, which in turn is based on a real API.
In this article, you will learn about some of the tools to test microservices running in a Kubernetes cluster. In particular, we will compare the Speedscale CLI tool with other tools and the main benefits of using Speedscale CLI. In the last few years, software companies have been shifting from building monolith applications to utilizing smaller microservices. In a microservices architecture, you operate with decentralized applications. This means that there's a separation in which each service is responsible for a specific component of your application.
With over 50,000 active organizations and 250 million workflows, CircleCI is one of the most popular networked CI platforms. When getting started with CI pipelines, teams typically want to ensure that code will compile, pass unit tests, and build a container image. After catching these low hanging fruit of syntax errors, engineering teams need to dig much further to find business logic and scalability errors.
In this tutorial, you will learn how to work with the gRPC Golang library for microservice communication by creating a simple note-taking application. APIs and service-to-service communication are what make modern microservice architecture possible. REST is generally the preferred implementation pattern, but if you only use REST, you could miss out on the significant performance gains that gRPC can offer. gRPC can provide better speed and efficiency than REST APIs.
Observability, introspection, logging, and dependency mapping are critical when building APIs. With the advent of microservice architecture, understanding what happens inside your container is vital during development. Speedscale CLI is a container-centric tool that allows you to monitor inbound and outbound traffic. With Speedscale CLI, you can monitor raw requests, latency, encoding, and detected technologies.
While new cloud native architectures are incredibly feature-rich, they can come with a high barrier to entry. Many getting started tutorials are pages long and can take forever to complete. But these always start with the first step of performing an installation. In the spirit of making the installation of Speedscale as simple as possible, we have designed a new interactive installer as part of the speedctl command line interface.
In this blog post we use podtato-head to demonstrate how to load test kubernetes microservices and how Speedscale can help understand the relationships between them. No, that's not a typo, podtato-head is an example microservices app from the CNCF Technical Advisory Group for Application Delivery, along with instructions on how to deploy it in numerous different ways. There are more than 10 delivery examples, you will surely learn something by going through the project. We liked it so much we forked the repo to contribute our improvements.
