12 nəticə — yol xəritələri, maaş bələdçiləri, sertifikatlar və iş bazarı təhlili.
Amazon Prime Video cut costs 90% by going back to a monolith. 42% of organizations consolidated microservices. The case studies nobody wants to talk about.
At 3 AM on a Tuesday, our payment service started timing out. Within minutes, the timeout cascaded: the order service hung waiting for payment responses, the API gateway filled its thread pool with pending order requests, and the entire platform went down. All because one database in one service was
BirJob scrapes 80+ job listing websites daily. Every single one of those sites is an API of some kind — whether it's a formal REST API or an HTML page we parse. And every single one has rate limits, even if they don't document them. I learned this the hard way when our scraper IP got banned from thr
Two years ago, I migrated BirJob's codebase from a polyrepo setup (separate repos for the frontend, the scraper, the API, and shared utilities) to a monorepo. Six months later, I migrated back. Then, a year after that, I moved to a monorepo again — this time with Turborepo and a much better understa
Last year, BirJob's main vacancies table crossed 800,000 rows. Queries that used to return in 12ms started taking 1.4 seconds. Our job search page — the single most important page on the site — became sluggish. I spent three weeks deep in Postgres internals, and the lessons I learned apply to any ap
Last month, I pushed a DNS change for BirJob's domain and then stared at my screen for 45 minutes wondering why the site was still resolving to the old IP. I knew about DNS propagation, I knew about TTLs, and I still made the same mistake every developer makes: I didn't lower the TTL before making t
I first encountered consensus algorithms when a Redis cluster split-brain incident took down our job queue at 4 AM. Three Redis nodes each thought they were the primary, accepting writes independently. When the network partition healed, we had three conflicting versions of the same data. The recover
I've used all four of these tools in production. Terraform for BirJob's infrastructure, CloudFormation at a previous job, Pulumi for a side project, and AWS CDK for a client engagement. Each has left scars and each has earned my respect. The "best" one depends entirely on your team, your cloud provi
Early in my career, I thought code reviews were about catching bugs. I'd leave dozens of comments about variable naming, missing semicolons, and style inconsistencies. My reviews were thorough. They were also demoralizing, unproductive, and often wrong about what actually mattered.
Async Python, 93 scraper files, 4-layer deduplication, and $0/month in compute costs. How BirJob scrapes Azerbaijan's entire job market every day on GitHub Actions' free tier.
I still remember the moment Terraform clicked for me. I was SSHing into a production server at 2 AM, manually running apt-get install nginx for the fourth time that month, when it hit me: I was being a human script runner. Everything I was doing could be — and should be — codified, versioned, and au
The first time I deployed BirJob to production, I did it the simplest way possible: SSH into the server, git pull, npm run build, pm2 restart. The site was down for 47 seconds while the build ran. No one noticed — we had maybe 10 users at the time.