Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 167
  1. WebRTC

    WebRTC is the browser stack for peer-to-peer audio, video, and data channels.

  2. Module federation

    Module Federation lets one JavaScript build load modules from another build at runtime.

  3. Traffic shifting is the capability that turns a service mesh from a fancy observability layer into a genuine deployment safety net.

  4. Partial hydration

    Mental model: hydrate less of what you already rendered Partial hydration is the practice of server-rendering a page while hydrating only the parts that need client-side behavior.

  5. CSS containment

    Containment gives the browser boundaries CSS containment lets an element promise that some of its internals do not affect the outside world.

  6. Background job queues are where the optimistic assumptions of synchronous code go to die.

  7. Selective hydration

    Mental model: hydration is scheduling, not just attaching events Hydration turns server-rendered HTML into an interactive client tree.

  8. Cold starts are the tax you pay for not running servers.

  9. Cumulative Layout Shift measures unexpected visual movement.

  10. Pod Disruption Budgets (PDBs) are one of the most misunderstood reliability primitives in Kubernetes.

  11. Referential equality

    Referential equality means two values are considered equal because they point to the same object, array, or function instance.

  12. Why bloat exists at all To understand index bloat you first have to understand a design decision at the heart of PostgreSQL: MVCC, multi-version concurrency control.

  13. ETag vs Cache-Control

    Mental model Cache-Control tells caches how long and under what rules a response can be reused.

  14. Backpressure in streams API

    Backpressure is the mechanism that prevents a fast producer from overwhelming a slow consumer.

  15. Shadow DOM

    Shadow DOM is an encapsulation boundary for DOM and CSS.

  16. Prepared Statement Caching

    What a prepared statement actually buys you Every SQL query the database receives goes through a pipeline before a single row is touched: it is parsed into a syntax tree, analyzed and rewritten (resolving table and column names, expanding views), and then…

  17. Islands architecture

    Mental model: static HTML with targeted interactivity Islands architecture starts from the assumption that most of a page can be delivered as inert HTML.

  18. Largest Contentful Paint measures when the largest visible content element in the viewport is painted.

  19. Subpixel rendering

    CSS pixels are not device pixels Modern layout is full of fractions.

  20. A failure that looks like everything else Connection pool exhaustion is one of the most common production incidents, and one of the most misdiagnosed.

  21. Server components

    Mental model: components can be a transport boundary Server Components move part of the component tree to the server.

  22. Read Replicas Lag Monitoring

    The promise and the catch Read replicas are the standard first move for scaling reads.

  23. HTTP/3 and QUIC

    Mental model HTTP/3 is HTTP semantics running over QUIC instead of TCP.

  24. Why shard at all A single database node has a ceiling.

  25. Memoization pitfalls

    Memoization caches the result of a computation for a set of inputs.

  26. AbortController

    AbortController is the web platform’s shared cancellation primitive.

  27. The dual-write problem Almost every service that owns data also needs to tell the rest of the system when that data changes.

  28. Custom Elements lifecycle

    Custom elements are classes that the browser upgrades into real DOM behavior.

  29. Most applications use a single data model for both writing and reading: the same tables, the same objects, the same schema serve commands that change data and queries that fetch it.

  30. Priority hints

    Mental model Priority Hints let developers nudge the browser’s internal fetch priority using fetchpriority.

  31. For two decades, the standard advice for writing scalable Java servers has been: never block a thread, because threads are expensive, so wrap everything in thread pools and reactive callbacks.

  32. Speculative prerendering

    Speculative prerendering loads and renders a likely future page before the user navigates to it.

  33. Why aggregate, and why sample A single modern service can emit tens of thousands of log lines per second.

  34. Streaming SSR

    Mental model: send the shell before every dependency is done Traditional server-side rendering waits until the whole page’s data and HTML are ready, then sends one response.

  35. IntersectionObserver answers a geometry question asynchronously IntersectionObserver tells you when a target intersects a root rectangle.

  36. Garbage collection is the JVM feature most developers ignore until a production incident forces them to care.

  37. Stale closure problem

    The stale closure problem occurs when a function keeps references to values from an old render, old state transition, or old lexical scope and then runs later as if those values were current.

  38. Streaming fetch response handling lets a page process bytes as they arrive instead of waiting for the entire response body.

  39. Mental model preload, prefetch, and preconnect are resource hints, but they solve different timing problems. preload says “this resource is needed for the current navigation; start it earlier.” prefetch says “this may be needed for a future navigation; fe…

  40. When a system grows beyond a single machine, the comfortable abstractions of in-process method calls break down.

  41. Edge rendering

    Mental model: move the first decision closer to the user Edge rendering runs request-time rendering logic in geographically distributed runtimes near the user.

  42. Web Components are most valuable at boundaries: design systems used across frameworks, embeddable widgets, long-lived platform components, and islands inside applications that change framework stacks over time.

  43. What cardinality actually means In Prometheus, a single metric name is not one thing.

  44. When a service needs to read or write large files, the choice between traditional stream-based I/O and memory-mapped files (mmap) can change throughput, latency, and memory behavior by an order of magnitude.

  45. Concurrency is hard because two independent activities can touch the same data at the same time and corrupt it.

  46. Priority inversion happens when high-priority work waits behind low-priority work.

  47. Mental model In a monolith, a stack trace tells you the whole story of a request.

  48. The distinction between macrotasks and microtasks explains many frontend timing bugs.

  49. CORS preflight

    Mental model CORS preflight is the browser asking a server for permission before sending a cross-origin request that could have side effects or expose non-simple behavior.

  50. Mental model In a distributed system, the dangerous failures are not the ones that crash a single service — they are the ones that cascade.