devops
24 posts
The exact IAM size, attach, and quota limits you will hit at scale, and the scoped-policy, permission-boundary, and SCP structure that keeps you far from every one.
aws · iam · security +2
Each git event deserves a different GitHub Actions job: what to run on push, pull_request, the merge queue, and tag/release, and why routing protects lead time.
ci-cd · github-actions · devops +1
How high-performing teams shrink the lead time from code-complete to live in production, without trading away security or code quality. A guide for tech leads.
ci-cd · devops · dora-metrics +2
How high-performing teams keep security review from becoming a lead-time bottleneck: shift-left automation, risk-based gates, a paved road, dependency cadence.
ci-cd · devops · security +3
Production deploys need a real approval gate: use GitHub Environments with native protection rules and scoped secrets, not workflow if: hacks or marketplace actions.
github-actions · ci-cd · devops +2
A practical guide to building an org-level shared GitHub Actions platform: architecture decisions, security governance, adoption, and 7 costly mistakes.
github-actions · ci-cd · devops +5
A technical guide to choosing and implementing AWS edge computing for global apps, with practical examples and cost optimization strategies.
aws · cloudfront · lambda +6
A technical guide comparing AWS Secrets Manager and Parameter Store, showing when to use each service with real-world implementation patterns and CDK examples.
aws · secrets-management · security +7
A production guide to feature flags in distributed systems, comparing LaunchDarkly, Unleash, and AWS AppConfig with examples for rollouts and A/B testing.
feature-flags · devops · ci-cd +5
A practical guide to building Internal Developer Platforms with golden paths, self-service infrastructure, and product thinking, using Backstage, Port, and AWS.
platform-engineering · developer-experience · aws +2
Build, secure, and deploy custom Model Context Protocol servers for internal systems in TypeScript, with authentication, monitoring, and Kubernetes deployment.
typescript · mcp · nodejs +5
Overcome CloudFormation's 500 resource limit with nested stacks, cross-stack references, SSM Parameter Store, and microstack architecture, shown in TypeScript CDK.
aws-cdk · infrastructure-as-code · aws +2
A beginner's guide to OpenTelemetry covering traces, metrics, and logs with practical implementation examples, common pitfalls, and a terminology glossary.
opentelemetry · observability · monitoring +4
A practical glossary of essential networking concepts for developers - from protocols and DNS to debugging tools and security basics.
networking · http · debugging +3
A practical guide to setting up a secure, affordable private server using VPS, Dokploy for deployments, and Cloudflared tunnels for secure access without exposing ports
docker · deployment · cloudflare +2
A practical introduction to Traefik for developers familiar with nginx. Learn core concepts, setup examples, and when to choose Traefik over traditional reverse proxies.
docker · networking · devops
Practical approaches to managing Lambda Layer versions across dev, staging, and production with AWS CDK, automated deployment pipelines, and rollbacks.
aws · lambda · aws-cdk +4
Learn to build automated preview environments using AWS CDK, Lambda, and GitHub Actions for seamless PR testing and review workflows
aws-cdk · serverless · ci-cd +5
A comprehensive guide to Claude Code, AI agents, and Model Context Protocol servers that transforms developers from basic users to power users
claude-code · mcp · ai-tools +5
A practical guide to AWS Fargate: task definitions, awsvpc networking, cost trade-offs, and when serverless containers beat managing EC2 hosts yourself.
aws · fargate · ecs +3
Advanced Fargate patterns learned from running production workloads. From cost optimization to stateful containers, here's what the docs won't tell you.
aws · fargate · ecs +4
How to deploy Fargate effectively with different IaC tools. Practical patterns, common gotchas, and what works best for each approach.
aws · fargate · aws-cdk +4
Protect your team from single points of failure through knowledge distribution, documentation strategies, and systematic risk management.
team-management · documentation · knowledge-sharing +5
Git branching strategies mapped to team size, product type, and release cadence. GitHub Flow is the default; here is when another model earns its overhead.
ci-cd · lessons-learned · team-management +3