Recent posts tagged backend

Description for Tag: "backend"

The server-side part of an application, responsible for logic, database interaction, and APIs.
Priyadharshiny13 • 20 hours • in Articles • 1 min read
Most resumes are filtered by ATS software before a human ever reads them. This project is a backend API that checks how well a resume matches a job description and suggests how to improve it. What it does PDF resume parsing: extracts text from uplo...
  • python
  • fastapi
  • docker
  • backend
Oamien • 3 days • in Articles • 9 min read
Introduction Booking a consultation should be straightforward for the person making the appointment. Behind the scenes, however, an automated booking system has to coordinate several moving parts: collecting customer information, checking availabi...
post-cover-32649
  • backend
  • javascript
  • node
  • tutorial
nyaomaru • Oct 23 • in Articles • 8 min read
Hoi hoi! YAY! is-kithttps://github.com/nyaomaru/is-kit just reached 100 GitHub stars⭐ 🎉🎉🎉 When it reached 50 stars, I wrote about how we use it in a production TypeScript application serving more than 100,000 users. 👇 https://dev.to/nyaomaru/is-ki...
post-cover-32180
  • typescript
  • opensource
  • frontend
  • backend
saurav_tb_pandey • Oct 19 • in Articles • 3 min read
What Are Write Concern and Read Concern? In MongoDB, write concern and read concern are configuration settings that specify the level of guarantee you require when saving or retrieving data across a distributed cluster. A write concern determines h...
  • mongodb
  • nodejs
  • database
  • backend
Chetan Chauhan • Oct 15 • in Tutorials • 1 min read
enter code here const express = require"express"; const app = express; const requests = new Map; const LIMIT = 5; const WINDOW = 60 1000; // 1 minute app.usereq, res, next => { const ip = req.ip; const now = Date.now; let data = request...
  • nodejs
  • backend
  • ratelimit
Mhamd Ghanoum • Oct 15 • in Articles • 2 min read
While testing a reconnect system for a deliverer-facing WebSocket gateway: when someone reconnects after losing their connection, they should get a snapshot of their current job plus any events they missed while offline. Two pieces, both of which I w...
  • backend
  • postgresql
  • nestjs
  • prisma
Tom Smithverified • 14 hours • in Articles • 9 min read
Security dominated this week, but not in the usual way. Two active campaigns turned GitHub configuration files into attack surfaces. Researchers demonstrated that the built-in browsers inside AI coding tools can read your SSH keys. And at Oracle AI ...
post-cover-33104
  • agenticai
  • devsecops
  • github
  • localai
Seungwon Lee • Oct 13 • in Articles • 7 min read
During an incremental system migration, I ran into a subtle consistency problem: our new service could successfully update the database while the legacy service continued reading stale data from its own in-memory cache. The obvious solutions such as...
  • distributedsystems
  • backend
  • architecture
Mhamd Ghanoum • Oct 12 • in Articles • 2 min read
I was fixing a real bug in a delivery backend I'm building: a customer's order could get created in Postgres even when something downstream failed, leaving an order with no event history behind it. The fix looked simple. Wrap the whole thing in pris...
post-cover-30791
  • prisma
  • postgresql
  • backend
  • typescript
Sudhanshu.thakur • Oct 11 • in Articles • 6 min read
AI agents are moving from chat interfaces into real business workflows. They can search customer records, update accounts, trigger deployments, and initiate financial operations. That creates a practical engineering question: what should happen betwe...
post-cover-30693
  • ai
  • ai-agents
  • mcp
  • backend
raylabs • Oct 10 • in Articles • 2 min read
Managing dependency recovery in serverless architectures requires coordinating multiple concurrent invocations to prevent a thundering-herd problem when a service heals. Quick solution: Coordinate the half-open lease through a single SQLite-backed Du...
post-cover-30668
  • reliability-engineering
  • serverless
  • backend
  • devops
raylabs • Oct 10 • in Articles • 3 min read
When a primary language model provider rejects requests due to location or transient overloads, many teams rely on an in-platform fallback tier. Logging response bodies and separating deterministic blocks from transient failures solves the diagnosis ...
post-cover-30571
  • backend
  • ai-agents
  • serverless
  • llm-integration
fazal_mansuri_ • Oct 9 • in Articles • 3 min read
Caching is one of the most powerful ways to improve application performance—reducing load times, server costs, and user frustration. Yet many developers treat caching as a “black box” or skip it due to fear of cache-related bugs. In this blog, we wi...
  • redis
  • backend
  • frontend
  • webperf
raylabs • Oct 9 • in Articles • 3 min read
Running a high-frequency automation system that triggers dozens of times per day creates a difficult reporting dilemma. If every run sends an immediate notification, your inbox fills with noise. If you turn off notifications entirely, regressions go ...
post-cover-30528
  • backend
  • serverless
  • devops
raylabs • Oct 9 • in Articles • 3 min read
When a poll-based reply bot runs in a staging environment, it usually behaves predictably. It reads recent posts, checks for mentions, and generates answers. In production, however, a user report reveals that a valid reply sat unanswered for hours wh...
post-cover-30521
  • backend
  • devops
  • ai-agents
raylabs • Oct 8 • in Articles • 3 min read
Offering a public demo of an Android application presents a unique architectural challenge. A demo build is exposed to strangers and needs frequent, destructive data resets, yet it must never be able to target or corrupt the real customer database by...
post-cover-30332
  • android
  • backend
  • application-security
  • architecture
raylabs • Oct 8 • in Articles • 3 min read
When an unattended cron system encounters a total provider failure, engineers often reach for a manual kill switch. While effective at stopping runaway requests, the manual-only reset pattern introduces hidden operational costs. If an outage lasts tw...
post-cover-30345
  • backend
  • devops
  • serverless
  • reliability
raylabs • Oct 8 • in Articles • 3 min read
When you want to publish multi-image carousels to Threads through its API, every item requires a publicly downloadable image URL. Traditional architectures solve this by uploading generated or processed assets to an object storage service like Amazon...
post-cover-30314
  • backend
  • serverless
  • api-integration
  • social-platforms
raylabs • Oct 8 • in Articles • 3 min read
A sync button can hide a destructive decision. When a spreadsheet and a backend database disagree because rows were added, removed, edited, duplicated, or marked for deletion, starting an automatic write without checking the shape of those difference...
post-cover-30272
  • backend
  • data-integrations
  • android
  • architecture
raylabs • Oct 8 • in Articles • 3 min read
A scheduled workflow can start successfully, finish with no eligible work, or commit an article that is not yet live. Counting all three as successes turns a reliability percentage into a trigger counter. Long-running and manually triggered execution...
post-cover-30245
  • backend
  • serverless
  • reliability
Stephen • Oct 7 • in Articles • 5 min read
Compared with traditional queue-based messaging platforms, Kafka is primarily designed for event streaming. It excels at distributing data from producers to one or many consumers at massive scale. However, unlike many traditional messaging platforms,...
post-cover-30143
  • architecture
  • eventdriven
  • kaft
  • backend
chevron_left
🔥 189 posts • 👩‍💻 111 active writers

✨ Want to write in this topic?
Share your learning. Get discovered. Build your profile.
Join CoderLegion

💡 Why developers use CoderLegion
Track learning • Share posts • Get ranked publicly
Create your profile