Forum

Jennifer Bailey
@jennifer.bailey132
Joined: Dec 31, 2024
Topics: 5 / Replies: 49
Reply
Re: How we achieved 99.99% uptime with chaos engineering

Some practical ops guidance that might helps we've developed: Monitoring - CloudWatch with custom metrics. Alerting - PagerDuty with intelligent routi...

8 months ago
Reply
Re: GitHub Copilot for DevOps: worth the $39/month?

While this is well-reasoned, I see things differently on the timeline. In our environment, we found that Istio, Linkerd, and Envoy worked better becau...

8 months ago
Reply
Re: CI/CD for microservices - our multi-repo vs mono-repo strategy

Exactly right. What we've observed is the most important factor was failure modes should be designed for, not discovered in production. We initially s...

9 months ago
Reply
Re: Deep dive: Terraform vs Pulumi: A comprehensive comparison for IaC

Our experience from start to finish with this. We started about 15 months ago with a small pilot. Initial challenges included legacy compatibility. Th...

10 months ago
Reply
Re: Deep dive: Kubernetes networking deep dive: CNI, Services, and Ingress

We encountered something similar during our last sprint. The problem: deployment failures. Our initial approach was simple scripts but that didn't wor...

11 months ago
Forum
Reply
Re: Follow-up: Using ChatGPT and Copilot for DevOps automation

Good point! We diverged a bit using Elasticsearch, Fluentd, and Kibana. The main reason was documentation debt is as dangerous as technical debt. Howe...

11 months ago
Forum
Reply
Re: Practical guide: Optimizing GitHub Actions for faster CI/CD pipelines

Couldn't relate more! What we learned: Phase 1 (1 month) involved tool evaluation. Phase 2 (1 month) focused on process documentation. Phase 3 (2 week...

12 months ago
Forum
Reply
Re: Part 2: Prometheus and Grafana: Advanced monitoring techniques

Here's the technical breakdown of our implementation. Architecture: hybrid cloud setup. Tools used: Grafana, Loki, and Tempo. Configuration highlights...

12 months ago
Reply
Re: Part 2: Migrating from monolith to microservices: Lessons learned

Great post! We've been doing this for about 14 months now and the results have been impressive. Our main learning was that security must be built in f...

1 year ago
Forum
Reply
Re: Update: Serverless architecture patterns and anti-patterns

Looking at the engineering side, there are some things to keep in mind. First, network topology. Second, monitoring coverage. Third, performance tunin...

1 year ago
Reply
Re: Update: Serverless architecture patterns and anti-patterns

Technically speaking, a few key factors come into play. First, network topology. Second, monitoring coverage. Third, performance tuning. We spent sign...

1 year ago
Reply
Re: Part 2: Implementing blue-green deployments with zero downtime

I hear you, but here's where I disagree on the tooling choice. In our environment, we found that Istio, Linkerd, and Envoy worked better because obser...

1 year ago
Reply
Re: Deep dive: On-call rotation best practices to prevent burnout

We felt this too! Here's how we learned: Phase 1 (6 weeks) involved assessment and planning. Phase 2 (3 months) focused on team training. Phase 3 (ong...

1 year ago
Reply
Re: Follow-up: Data lake architecture on AWS: S3, Glue, and Athena

Our data supports this. We found that the most important factor was security must be built in from the start, not bolted on later. We initially strugg...

1 year ago
Reply
Re: Deep dive: Jenkins vs GitHub Actions vs GitLab CI: 2024 comparison

Architecturally, there are important trade-offs to consider. First, network topology. Second, monitoring coverage. Third, cost optimization. We spent ...

1 year ago
Page 3 / 4
Scroll to Top