Kubernetes is becoming a dominant platform for running workloads. As the Kubernetes ecosystem continues to advance capturing a wider swath of workloads, eventually your code might be headed to Kubernetes. As a Tech Lead at Shipa responsible for front-end engineering e.g what you see on the screen, my job crosses JavaScript Frameworks and Kubernetes on a daily basis.

For those who aren’t that familiar with it, Electron is an open-source framework that allows developers to build cross-platform desktop applications in JavaScript. Some of the most popular desktop applications like VS Code, Slack, Discord, and Atom, are all built in Electron.

In our Configuring OpenTelemetry in Ruby blog post, we showed how to configure OpenTelemetry in a Ruby on Rails backend. In this post, we’ll cover how to configure OpenTelemetry in the front-end JavaScript in order to measure performance of browser and mobile devices and how to configure distributed tracing to work across the frontend and back end telemetry collection. Let’s dive in!

SDKs naturally increase in size over time. After all, it does take more bytes to implement more features. This is not a big deal for most languages—the relative size of each new feature is small, and load times and storage aren’t big concerns for code running on a server.

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.

Choosing a JavaScript framework for a new project can be a daunting task. There’s always a new one getting hype from the community, while the established players still have a lot to offer. So you need to do your homework and make sure the framework you choose is the right one for your specific requirements. Popularity alone is never the best indicator, but a review of the most widely-used options should help you decide which way to go.