Systems | Development | Analytics | API | Testing

5G is in the process of transforming communications technology, enabling never-before-seen data transfer speeds and high-performance remote computing capabilities.

Microservices have become a popular way to architect applications, particularly those that compose functionality from a variety of loosely coupled systems and services. While there are a variety of frameworks and tools for implementing a microservice architecture, it isn’t always clear how to expose native code like C or C++ code within a wider microservice system. That’s where HydraExpress comes in.

In this first section, I’ll provide a quick overview of the business case and the tools you can use to create a Kubernetes ingress API gateway. If you’re already familiar, you could skip ahead to the tutorial section. Digital transformation has led to a high velocity of data moving through APIs to applications and devices. Companies with legacy infrastructures are experiencing inconsistencies, failures and increased costs. And most importantly, dissatisfied customers.

As a team we have spent many years troubleshooting performance problems in production systems. Applications have gotten so complex you need a standard methodology to understand performance. Fortunately right now there are a couple of common frameworks we can borrow from: Despite using different acronyms and terms, they fortunately are all different ways of describing the same thing.

Not until the early did the concept of a container-based application emerge to transform the IT world. For the first time, the software was deployed consistently and reliably regardless of the target environment’s changes (private or public cloud, personal computer, etc.). With the development of containers, container orchestration has become a trending topic in recent years, with successful applications from the likes of tech giants Facebook, Google, Netflix, among others.

Deciding whether to run applications in containers or virtual machines used to entail analyzing which trade-offs you could accept in exchange for certain advantages. With Firecracker, we can leverage the benefits of both technologies. In this blog post, we are going to talk about why exactly Firecracker is setting the serverless computing world on fire and what you need to know about this emerging technology.

When making changes to applications these days, it’s hard to understand and predict the impact of those changes before you deploy. API connections are multiplying, and with new cloud platforms such as containers/serverless, it only add to the complexity. Some people have trouble remembering whether they closed the garage door or turned off the coffee maker. Can you remember all the details of your latest API contract change? Let alone who would be impacted and needed to be notified?

Nowadays developers are in the driver’s seat regarding a lot of decisions for the tools they use. In this update from Tyler Jewell, he covers what he sees are the Top 5 trends that will take place this year. While it’s a bit of a crowded chart, he plots the companies that he sees driving these trends. If you drill into the Service Catalog trend, Jewell sees a couple of different groups working on ways to help developers deal with the deluge of Services (aka APIs).

Innovation in hypervisor technology in the early 2000’s from both commercial and open source projects was the genesis for the public cloud as we know it today. Virtualization and Moore’s law, together with advances in storage technology, mobile and wireless, created a data explosion that continues to accelerate through today.

GKE is a Google Cloud service that offers a managed Kubernetes cluster, the nodes of the clusters are running on Google Cloud VM instances, the control plane and network is fully managed by GKE. GKE offers a sandboxing feature (https://cloud.google.com/kubernetes-engine/docs/concepts/sandbox-pods ), based on gVisor (https://gvisor.dev/docs/ ) it protects the host kernel from untrusted code.