![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
loopback4-kafka-client
Advanced tools
A Kafka Client for Loopback4 built on top of KafkaJS.
Install KafkaConnectorComponent using npm
;
$ [npm install | yarn add] loopback4-kafka-client
Configure and load KafkaConnectorComponent in the application constructor as shown below.
import {
KafkaClientBindings,
KafkaClientComponent,
KafkaClientOptions,
} from 'loopback4-kafka-client';
// ...
export class MyApplication extends BootMixin(
ServiceMixin(RepositoryMixin(RestApplication)),
) {
constructor(options: ApplicationConfig = {}) {
this.configure<KafkaClientOptions>(KafkaClientBindings.Component).to({
initObservers: true, // if you want to init consumer lifeCycleObserver
topics: [Topics.First], // if you want to use producers for given topics
connection: {
// refer https://kafka.js.org/docs/configuration
brokers: [process.env.KAFKA_SERVER ?? ''],
},
});
this.bind(KafkaClientBindings.ProducerConfiguration).to({
// your producer config
// refer https://kafka.js.org/docs/producing#options
});
this.bind(KafkaClientBindings.ConsumerConfiguration).to({
// refer https://kafka.js.org/docs/consuming#options
groupId: process.env.KAFKA_CONSUMER_GROUP,
});
this.component(KafkaClientComponent);
// ...
}
// ...
}
Producers and Consumers work on a Stream
which defines the topic and events used by the application. You can implement the IStreamDefinition
to create your own stream class.
export class TestStream implements IStreamDefinition {
topic = Topics.First;
messages: {
// [<event type key from enum>] : <event type or interface>
[Events.start]: StartEvent;
[Events.stop]: StopEvent;
};
}
A Consumer is a loopback extension
that is used by the KafkaConsumerService
to initialize consumers. It must implement one of the IConsumer
, ISharedConsumer
or IGenericConsumer
interfaces and should be using the asConsumer
binding template. If you want the consumers to start at the start of your application, you should pass the initObservers
config to the Component configuration.
IConsumer
- simple consumer for 1 event in a streamISharedConsumer
- consumer that consumes data for multiple events in a stream (defined with an array of events)IGenericConsumer
- consumer that consumes data for all events in a stream/topic (defined without any event). By default it is not triggered for an event if a more specific consumer is bound for that event. This behaviour can be changed using the alwaysRunGenericConsumer
option in consumer configuration.You can bind any consumer related configuration using the KafkaClientBindings.ConsumerConfiguration
key. It accepts all the options of KafkaJS, along with an additional option - alwaysRunGenericConsumer
- this option runs any generic consumer if available always, even if more specific consumers are bound by the client(only the specific consumer would run if this option is false or not provided).
// application.ts
this.configure(KafkaConnectorComponentBindings.COMPONENT).to({
...
initObservers: true
...
});
// start.consumer.ts
// use @genericConsumer for a generic consumer
@consumer<TestStream, Events.start>()
export class StartConsumer implements IConsumer<TestStream, Events.start> {
constructor(
@inject('test.handler.start')
public handler: StreamHandler<TestStream, Events.start>,
) {}
topic = Topics.First;
event: Events.start = Events.start;
// you can write the handler as a method
handler(payload: StartEvent) {
console.log(payload);
}
}
If you want to write a shared handler for different events, you can use the eventHandlerKey
to bind a handler in the application -
// application.ts
this.bind(eventHandlerKey(Events.Start)).to((payload: StartEvent) => {
console.log(payload);
});
this.bind(eventHandlerKey<TestStream, Events.Stop>(Events.Stop)).toProvider(
CustomEventHandlerProvider,
);
and then you can use the handler using the @eventHandler
decorator -
// start.consumer.ts
@consumer<TestStream, Events.start>()
export class StartConsumer implements IConsumer<TestStream, Events.start> {
constructor(
@eventHandler<TestStream>(Events.Start)
public handler: StreamHandler<TestStream, Events.start>,
) {}
topic = Topics.First;
event: Events.start = Events.start;
}
A Producer is a loopback service for producing message for a particular topic, you can inject a producer using the @producer(TOPIC_NAME)
decorator.
Note: The topic name passed to decorator must be first configured in the Component configuration's topic property -
If you want to produce a raw message without any event type, you can use the @genericProducer(TOPIC_NAME)
decorator, note that in this case, the topic name must be passed in the genericTopics property of the component configuration.
// application.ts
...
this.configure(KafkaConnectorComponentBindings.COMPONENT).to({
...
topics: [Topics.First],
...
});
...
// test.service.ts
...
class TestService {
constructor(
@producer(Topics.First)
private producer: Producer<TestStream>
) {}
}
FAQs
loopback client for integration with apache kafka
We found that loopback4-kafka-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.