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 (AMQP):
  • Example (REDIS):
  1. Other
  2. API reference
  3. messaging

messagingClient

Creates messaging client reader for given transport layer

PreviouseventBusNextcreateMicroservice

Last updated 4 years ago

Importing

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

Type declaration

messagingClient :: MessagingClientConfig
    -> Reader<Context, Promise<MessagingClient>>

Parameters

parameter

definition

config

MessagingClientConfig

MessagingClientConfig

parameter

definition

msgTransformer

<optional> TransportMessageTransformer

transport

options

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

To learn more about messagingClient output interface please visit:

Example (AMQP):

import { bindEagerlyTo, createContextToken } from '@marblejs/core';
import { messagingClient, Transport } from '@marblejs/messaging';

const AmqpClientToken = createContextToken<MessagingClient>('AmqpClient');

const AmqpClient = messagingClient({
  transport: Transport.AMQP,
  options: {
    host: 'amqp://localhost:5672',
    queue: 'some_queue_name',
    queueOptions: { durable: false },
    timeout: 360 * 1000,
  },
});

...

const dependencies = [
  bindEagerlyTo(AmqpClientToken)(AmqpClient),
];

Example (REDIS):

import { bindEagerlyTo, createContextToken } from '@marblejs/core';
import { messagingClient, Transport } from '@marblejs/messaging';

const RedisClientToken = createContextToken<MessagingClient>('RedisClient');

const RedisClient = messagingClient({
  transport: Transport.REDIS,
  options: {
    host: 'redis://127.0.0.1:6379',
    channel: 'some_channel_name',
    timeout: 360 * 1000,
  },
});

...

const dependencies = [
  bindEagerlyTo(RedisClientToken)(RedisClient),
];

Transport (see: )

StrategyOptions (see: )

#bindEagerlyTo
Microservices
#createMicroservice
#createMicroservice