| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| The $1,000 AWS mistake |
| |
| |
A missing VPC Gateway Endpoint sent EC2-to-S3 traffic through a NAT Gateway, lighting up over $1,000 in unnecessary data processing charges. All that for in-region traffic hitting an AWS service.
Why? AWS defaulted the route to the NAT Gateway. It only takes the free S3 Gateway Endpoint if you tell it to.
The lesson: Cloud networks aren’t simple. If you don’t shape the traffic, AWS will - expensively. |
|
| |
|
| |
|
| |
| Terraform Workbook - Your Guide to Infra as Code (IaC) |
| |
| |
| This post outlines the various Terraform project files and their purposes, such as vars.tf for default variable declarations, terraform.tfvars for overriding default variable values, terraform.tf for tfstate backends and provider declarations, version.tf for Terraform version constraints, and .terraform.lock.hcl for dependency snapshots. Additional files in a Terraform project, like network.tf or database.tf, contain modules or provider resources for managing infrastructure. The post also includes examples of variables, tf files for Azure and Google Cloud, version constraints, and running Terraform commands like init, plan, apply, state manipulation, force-unlock, and taint. |
|
| |
|
| |
|
| |
| A Love Letter to FreeBSD |
| |
| |
A Linux user takes FreeBSD for a spin - and comes away impressed. What stands out? Clean, deliberate engineering. Boot environments make updates stress-free. The new pkgbase system adds modularity without chaos. And the OS treats uptime not just as a metric, but as a design goal.
The essay makes a solid case: decouple fast-moving desktops from server-grade stability. Tie OS evolution to hardware lifecycles that don’t panic every 6 months. |
|
| |
|
| |
|
| |
| The AI Gold Rush Is Forcing Us to Relearn a Decade of DevOps Lessons |
| |
| |
Sauce Labs just dropped a reality check: 95% of orgs have fumbled AI projects. The kicker? 82% don’t have the QA talent or tools to keep things from breaking. Even worse, 61% of leaders don’t get software testing 101, leaving AI pipelines full of holes - cultural, procedural, and otherwise.
System shift: Agentic AI is crashing headfirst into old-school DevOps. Speed’s winning. Quality’s bleeding. |
|
| |
|
| |
|
| |
| How Netflix optimized its petabyte-scale logging system with |
| |
| |
Netflix overhauled its logging pipeline to chew through 5 PB/day. The stack now leans on ClickHouse for speed and Apache Iceberg to keep storage costs sane.
Out went regex fingerprinting - slow and clumsy. In came a JFlex-generated lexer that actually keeps up. They also ditched generic serialization in favor of ClickHouse’s native protocol and sharded log tags to kill off unnecessary scans and trim query times.
Bigger picture: More teams are building bespoke ingest pipelines, tying high-throughput data flow to layered storage. Observability is getting the same kind of love as prod traffic. Finally. |
|
| |
|
| |
|
| |
| Test Automation Structure for Single Code Base Projects |
| |
| |
| The authors discuss the development of a new automation infrastructure post-merger, leading to a unified automation project that can handle all cultures, languages, and clients efficiently. They chose Playwright over Cypress for its improved resource usage and faster execution times, aligning better with their expanding requirements. Additionally, they introduced a centralized npm package to address common needs across teams, reducing code duplication and maintenance costs while improving test reliability and readability. |
|
| |
|
| |
|
| |
| Self Hostable Multi-Location Uptime Monitoring |
| |
| |
Vigilant runs distributed uptime checks with self-registering Go-based "outposts" scattered across the globe. Each one handles HTTP and Ping, reports back latency by region, and calls home over HTTPS.
The magic handshake? Vigilant plays root CA, handing out ephemeral TLS certs on the fly. |
|
| |
|
| |
|
| |
| Collaborating with Terraform: How Teams Can Work Together Without Breaking Things |
| |
| |
| When working with Terraform in a team environment, common issues may arise such as state locking, version mismatches, untracked local applies, and lack of transparency. Atlantis is an open-source tool that can help streamline collaboration by automatically running Terraform commands based on GitHub pull requests. Setting up Atlantis locally with Docker and ngrok allows for a transparent and auditable process where every plan and apply is visible in the same place as the code review. |
|
| |
|
| |
|
| |
| How when AWS was down, we were not |
| |
| |
During the AWS us-east-1 meltdown - when DynamoDB, IAM, and other key services went dark - Authress kept the lights on. Their trick? A ruthless edge-first, multi-region setup built for failure.
They didn’t hope DNS would save them. They wired in automated failover, rolled their own health checks, and watched business metrics - not just system metrics - for signs of trouble. That combo? It worked.
To chase a 99.999% SLA, they stripped out weak links, dodged flaky third-party services, and made all compute region-agnostic. DynamoDB Global Tables handled global state. CloudFront + Lambda@Edge took care of traffic sorcery.
The bigger picture: Reliability isn’t a load balancer’s job anymore. It starts in your architecture. Cloud provider defaults? Not enough. Build like you don’t trust them. |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
