LogoLogo
ChangelogGitHubTwitterGitter
v3.x
v3.x
  • Marble.js
  • Getting started
    • Installation
    • Quick setup
  • HTTP
    • Effects
    • Middlewares
    • Routing
    • Errors
    • Output
    • Context
    • Advanced
      • Logging
      • Validation
      • Server Events
      • Streaming
      • Continuous mode
  • Messaging
    • Core concepts
      • Events
      • Effects
    • Microservices
      • AMQP (RabbitMQ)
      • Redis Pub/Sub
    • CQRS
    • WebSockets
  • Testing
    • HTTP routes testing
  • Other
    • How does it glue together?
    • Migration guides
      • Migration from version 2.x
      • Migration from version 1.x
    • API reference
      • core
        • bindTo
        • bindEagerlyTo
        • createEvent
        • createServer
        • combineRoutes
        • createContextToken
        • EffectFactory
        • r.pipe
        • httpListener
        • operator: matchEvent
        • operator: use
        • operator: act
      • messaging
        • eventBus
        • messagingClient
        • createMicroservice
        • reply
      • websockets
        • webSocketListener
        • operator: broadcast
        • operator: mapToServer
      • middleware-multipart
      • middleware-cors
      • middleware-joi
      • middleware-jwt
        • Token signing
      • middleware-io
      • middleware-logger
      • middleware-body
    • Style Guide
    • FAQ
Powered by GitBook
On this page
  • Importing
  • Type declaration
  • Parameters
  • Example
  1. Other
  2. API reference
  3. messaging

eventBus

Creates messaging client reader for LOCAL transport layer (Event Bus)

PreviousmessagingNextmessagingClient

Last updated 4 years ago

Importing

import { eventBus } from '@marblejs/messaging';

Type declaration

eventBus :: EventBusConfig
  -> Reader<Context, Promise<TransportLayerConnection>>

Parameters

parameter

definition

config

EventBusConfig

EventBusConfig

parameter

definition

listener

<optional> MessagingListener

Because of asynchronous nature of messaging client, all related readers have to be bound to server creators via eager binding 👉

To learn more about eventBus usage please visit:

Example

The event bus can be attached to server creator, like basic HTTP or any other microservice.

@marblejs/messaging module exposes already existing messaging client for eventBus transport layer:

import { eventBus } from '@marblejs/messaging';

Additionally it exports tokens for both EventBus and EventBusClient instances.

import { EventBusToken, EventBusClientToken } from '@marblejs/messaging';
import { httpListener, createServer, bindEagerlyTo } from '@marblejs/core';
import { messagingListener, EventBusToken, EventBusClientToken, eventBusClient, eventBus } from '@marblejs/messaging';
​
const eventBusListener = messagingListener(...);
const listener = httpListener(...);
​
export const server = createServer({
  listener,
  dependencies: [
    bindEagerlyTo(EventBusClientToken)(eventBusClient),
    bindEagerlyTo(EventBusToken)(eventBus({ listener: eventBusListener })),
  ],
});
​
const main: IO<void> = async () =>
  await (await server)();
​
main();
#bindEagerlyTo
CQRS