A software design pattern where the flow of the program is determined by events (state changes, messages, user actions). In Solana dApps: WebSocket subscriptions trigger callbacks on account changes, Anchor events (emit!) notify clients of on-chain state transitions, and transaction logs are parsed for event data. Enables reactive, real-time user interfaces.
Empieza por la explicación más corta y útil antes de profundizar.
A software design pattern where the flow of the program is determined by events (state changes, messages, user actions). In Solana dApps: WebSocket subscriptions trigger callbacks on account changes, Anchor events (emit!) notify clients of on-chain state transitions, and transaction logs are parsed for event data. Enables reactive, real-time user interfaces.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Serialización, memoria, estructuras de datos y bases de ingeniería.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
Event-Driven Architecture (event-driven) Categoría: Fundamentos de Programación Definición: A software design pattern where the flow of the program is determined by events (state changes, messages, user actions). In Solana dApps: WebSocket subscriptions trigger callbacks on account changes, Anchor events (emit!) notify clients of on-chain state transitions, and transaction logs are parsed for event data. Enables reactive, real-time user interfaces. Relacionados: Suscripciones WebSocket, Anchor Events (emit!)
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
A persistent bidirectional connection to a Solana RPC node's WebSocket endpoint (typically on port 8900) that allows clients to receive real-time push notifications when on-chain state changes, rather than polling via HTTP. The subscription model supports account changes, program account changes, slot updates, root changes, signature confirmations, and log emission, each returning a subscription ID used to later unsubscribe.
Anchor's event system using the `emit!()` macro. Events are defined with `#[event]` on structs and emitted as base64-encoded data in program logs (prefixed with a discriminator). Clients subscribe via `program.addEventListener('EventName', callback)`. Events cost compute units for logging and are limited by the 10KB log size.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
A persistent bidirectional connection to a Solana RPC node's WebSocket endpoint (typically on port 8900) that allows clients to receive real-time push notifications when on-chain state changes, rather than polling via HTTP. The subscription model supports account changes, program account changes, slot updates, root changes, signature confirmations, and log emission, each returning a subscription ID used to later unsubscribe.
Anchor's event system using the `emit!()` macro. Events are defined with `#[event]` on structs and emitted as base64-encoded data in program logs (prefixed with a discriminator). Clients subscribe via `program.addEventListener('EventName', callback)`. Events cost compute units for logging and are limited by the 10KB log size.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
A systems programming language emphasizing memory safety, zero-cost abstractions, and concurrency without a garbage collector. Rust uses an ownership model with borrow checking at compile time to prevent data races and null pointer bugs. It is the primary language for Solana program development (via Anchor or native solana-program crate) and the Agave validator client.
A statically typed superset of JavaScript that compiles to plain JavaScript. TypeScript adds type annotations, interfaces, generics, and enums to catch errors at compile time. It is the standard language for Solana client-side development—wallet adapters, dApp frontends, test suites, and SDK interactions (web3.js, Anchor client) are typically written in TypeScript.
The ubiquitous scripting language for web development, running in browsers and Node.js. JavaScript is dynamically typed and event-driven. Most Solana dApp frontends and scripts use JavaScript/TypeScript with libraries like @solana/web3.js. Node.js enables server-side JS for backend services, indexers, and bot development.
A JavaScript runtime built on Chrome's V8 engine that enables server-side JavaScript execution. Node.js uses an event-driven, non-blocking I/O model. In the Solana ecosystem, Node.js is used for: running Anchor tests (Mocha/Jest), backend services, transaction bots, indexers, and CLI tools. npm/yarn/pnpm manage JavaScript package dependencies.