Explore >> Select a destination
|
You are here 
|
blog.nuculabs.de | ||
| | | | |
vadosware.io
|
|
| | | | | It took way more trial and error than I expected to set up E2E testing for a python-based project on CircleCI -- my loss (of time) is your gain. | |
| | | | |
vsupalov.com
|
|
| | | | | Notes on how to set up the right python version and and isolated development environments. | |
| | | | |
jessitron.com
|
|
| | | | | TL;DR: skip to this readme for the easiest path When you're running applications in Kubernetes, and you're using OpenTelemetry for observability, then one recommended practice is to run the OpenTelemetry Collector on each node in your cluster. Then each of your applications can send telemetry data (traces, metrics, logs) to that local collector. To run | |
| | | | |
sookocheff.com
|
|
| | | Disaster events are one of the biggest challenges that a software organization can face. Natural disasters like earthquakes or floods, technical failures such as power or network loss, and human actions such as unauthorized attacks can disable an entire fleet of systems, leading to complete failure for a business. To deal with disaster scenarios requires a proactive approach to prepare and recover from failure. One of the key benefits of running in the cloud is how easy it is to run workloads in multiple regions. This allows you to deploy a resilient architecture that supports disaster recovery, even in the cases where an entire region is disabled. | ||
