Chaos Engineering for Cloud native Apps

Chaos Engineering for Cloud native Apps

Published on 2022-11-03

Improve application resilience with chaos testing by deliberately introducing faults that simulate real-world outages. Azure Chaos Studio Preview / AWS Fault Injection Simulator is a fully managed chaos engineering experimentation platform for accelerating discovery of hard-to-find problems, from late-stage development through production. Disrupt your apps intentionally to identify gaps and plan mitigations before your customers are impacted by a problem.

Related Content

Deploying a multi-region Serverless API Layer (Part 1)

2019-07-13 · 4 min

In my spare time, I work on a pet project called Theatreers. The aim of this is a microservice based platform focused on Theatre / Musical Theatre (bringing a few of my passion areas together). I've recently re-architected the project to align to a multi-region serverless technology stack.

Microservices have communication issues, especially when they fail

Microservices have communication issues, especially when they fail

2022-09-01

Communication between entities has been a long lasting topic in Software engineering. IPC, Message brokers, Queues are only few of the main actors in this drama. In this episode, Chris is joined by Francesco who will cover a couple of Microservices communication patterns and give a deep dive into the Saga pattern to resolve multi-step transaction flows.

ClickOps over GitOps

ClickOps over GitOps

2022-10-27

The delta between Kubernetes and a developer friendly PaaS is where the next layer of value is being created today. Many products are racing to fill the void that is called Kubernetes developer experience. This is also the place where things get opinionated, a requirement for reliable end to end workflows. In this talk you will learn about Gimlet.io's approach on how Kubernetes UIs can be quick to use, and safe at the same time. In this talk you will see how you can create a developer platform - with the usual components Cert-Manager, Nginx Ingress etc - and deploy on it with only clicking on a dashboard. You will also see that behind the curtains, all Gimlet does is writing yamls into a git repository. ClickOps.. over GitOps.