#Web Development

Articles about Web Development — exploring patterns, best practices, and real-world implementations in production systems.

6 posts tagged with web development. ← All posts

#A2A (14)#ADK (8)#AG-UI (6)#AI (9)#AI Agents (303)#AI Architecture (10)#AI Cost (10)#AI Cost Optimization (8)#AI Engineering (160)#AI Governance (28)#AI Red Teaming (9)#AI Research (9)#AI Safety (6)#AI Security (21)#AI in Production (12)#AML (3)#API Design (10)#API Security (8)#APIs (47)#AWS (17)#Accounting (9)#Agent Skills (3)#Agentic AI (24)#Agentic Commerce (12)#Agentic RAG (8)#Agents (4)#Amazon Bedrock (8)#Architecture (36)#Audit (3)#Authentication (10)#Authorization (3)#Automation (6)#Azure (11)#Azure AI Foundry (9)#Backend Engineering (267)#BigQuery (6)#CI/CD (8)#Capital Markets (14)#Card Payments (12)#Cards (13)#Career (7)#Checkpointing (4)#Claude Code (8)#Cloud (3)#Cloud Architecture (3)#Code Review (8)#Collaboration (4)#Communication (4)#Compliance (51)#Computer Networking (8)#Concurrency (25)#Consulting (3)#Context Engineering (10)#Cost Optimisation (5)#Credit (14)#Credit Risk (14)#CrewAI (8)#Crypto (12)#Cryptocurrency (12)#Custody (9)#DSPy (8)#Data (4)#Data Engineering (4)#Data Structures (8)#Databases (33)#Deployment (3)#DevOps (9)#DevSecOps (11)#Developer Experience (5)#Distributed Systems (88)#Documentation (3)#Edge AI (8)#Embeddings (14)#Engineering (7)#Engineering Culture (3)#Engineering Practices (16)#Evaluation (44)#Event-Driven Architecture (8)#FREE-AI (8)#FX (5)#FinOps (23)#FinTech (6)#Financial AI (14)#Financial Systems (129)#Fine-Tuning (11)#Fintech (131)#Flutter (8)#Foreign Exchange (5)#Forward Deployed Engineer (8)#Forward Deployed Engineering (8)#Fraud (10)#Function Tools (5)#GCP (5)#Gemma (4)#Go (220)#Google ADK (36)#Governance (55)#Granite (6)#GraphQL (3)#Guardrails (24)#HIPAA (3)#HTTP (3)#Harness Engineering (8)#Hugging Face (8)#Human-in-the-Loop (8)#IBM watsonx (8)#Identity (11)#Integration (3)#Interfaces (3)#KYC (11)#KYC and AML (12)#Kafka (10)#Kubernetes (9)#LLM (5)#LLM Inference (8)#LLMs (110)#LangChain (8)#LangGraph (11)#Ledger (12)#Lending (14)#LlamaIndex (8)#MCP (22)#MLOps (30)#Machine Learning (13)#Markets (4)#Memory (13)#Memory Management (4)#Microservices (3)#Microsoft Agent Framework (150)#Middleware (6)#Migration (9)#Monitoring (3)#Multi-Agent (10)#Multi-Agent AI (14)#Multi-Agent Systems (70)#Multimodal (3)#NIM (5)#NVIDIA (8)#OAuth (3)#OWASP (7)#Observability (43)#On-Device AI (8)#Open Source (6)#OpenTelemetry (5)#Opinion (6)#Orchestration (10)#Payment Rails (16)#Payments (54)#Performance (29)#Platform Engineering (9)#Privacy (4)#Privacy Engineering (3)#Product (4)#Production (6)#Programming (10)#Programming Languages (16)#Prompt Engineering (64)#Prompt Injection (6)#Protocols (9)#Providers (4)#Pydantic AI (8)#Python (142)#Quality (3)#RAG (58)#RBI (3)#REST (5)#Rails (16)#Reconciliation (3)#RegTech (8)#Regulation (9)#Reliability (45)#Resilience (3)#Responsible AI (5)#Retrieval (3)#Risk (13)#Rust (16)#SRE (20)#Scalability (3)#Security (80)#Self-Evolving Agents (16)#Sessions (3)#Settlement (9)#Software Architecture (35)#Software Engineering (138)#Spanner (4)#Strands (8)#Streaming (25)#Structured Output (4)#System Design (32)#Systems Programming (16)#Testing (34)#Tool Use (21)#Tools (3)#Trading (8)#Treasury (6)#Type System (3)#Type Systems (3)#Vector Databases (21)#Vector Search (11)#Web Development (6)#Workflows (14)#gRPC (5)#smolagents (8)
Pratik Dhanave · ·7 min read

Sessions, Single Sign-On, and Logout

Logging a user in is the easy part; keeping them logged in — and, harder than anyone expects, logging them out — is where identity gets subtle. Sessions bridge stateless requests into a continuous identity, single sign-on shares that identity across apps, and single logout is a genuinely hard problem that most systems get partly wrong.

Logging a user in is the easy part; keeping them logged in — and, harder than anyone expects, logging them out — is where identity gets subtle. Single logout is a genuinely hard problem that most systems get partly wrong.

Pratik Dhanave · ·7 min read

HTTP Evolution: 1.1 to 2 to 3

HTTP is the protocol your applications actually speak, and it has quietly reinvented itself twice to fight one persistent enemy: head-of-line blocking, where one slow thing stalls everything behind it. The journey from HTTP/1.1 to HTTP/2 to HTTP/3 is the story of chasing that problem down the stack — and understanding it explains why modern connections are so much faster.

HTTP is the protocol your applications speak, and it has quietly reinvented itself twice to fight one enemy: head-of-line blocking, where one slow thing stalls everything behind it. The journey from HTTP/1.1 to 2 to 3 is chasing that problem down the stack.

Pratik Dhanave · ·6 min read

TLS and HTTPS

The "s" in HTTPS is TLS, and it does three things at once that most engineers conflate: it encrypts the connection, verifies you're talking to the real server, and detects tampering. Understanding how — the handshake, the certificates, the chain of trust — demystifies the padlock icon and the certificate errors that block deploys, and it's foundational to every secure connection you make.

The 's' in HTTPS is TLS, and it does three things engineers often conflate: encrypts the connection, verifies you're talking to the real server, and detects tampering. Understanding the handshake, certificates, and chain of trust demystifies the padlock and the cert errors.

Pratik Dhanave · ·6 min read

DNS

DNS is the internet's phone book — it turns the names humans use into the addresses machines route to — and it's also the internet's most common outage cause and a frequent source of baffling latency. "It's always DNS" is a running joke among engineers precisely because DNS is invisible until it breaks, and then it breaks everything.

DNS is the internet's phone book — it turns the names humans use into the addresses machines route to — and it's also the internet's most common outage cause. 'It's always DNS' is a running joke because DNS is invisible until it breaks, and then it breaks everything.

Pratik Dhanave · ·6 min read

The Network Stack

Every backend engineer relies on the network constantly and understands it vaguely — until a mysterious timeout, a TLS error, or a latency spike forces a reckoning. The layered model of networking is the map that makes those problems legible: each layer does one job, hides the one below it, and fails in its own characteristic way. Learn the layers and the network stops being magic.

Every backend engineer relies on the network constantly and understands it vaguely — until a mysterious timeout or TLS error forces a reckoning. The layered model is the map that makes those problems legible: learn the layers and the network stops being magic.

Pratik Dhanave · ·6 min read

Authentication vs Authorization

Half of all identity confusion — and a surprising share of security bugs — comes from blurring two words that sound alike and mean opposite things. Authentication asks "who are you?"; authorization asks "what are you allowed to do?" Every protocol in this series exists to answer one or the other, and mixing them up is how you build systems that are both insecure and broken.

Half of all identity confusion — and a surprising share of security bugs — comes from blurring two words: authentication asks 'who are you?', authorization asks 'what are you allowed to do?' Every protocol in this series answers one or the other.

All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.