EventStore-Client-NodeJS
EventStore-Client-NodeJS copied to clipboard
EventStore
A NodeJS client for Event Store
- immediately cache the promise and await the promise on subsequent appends - rework backpressured write to work across multiple calls to shared stream - add test fixes #304 fixes:...
Reproduction steps: 1. Setup the test client: https://github.com/EventStore/test-client-node 2. Setup an EventStore 20.10.2 Cluster with 2 vCPUs and 4 GB of memory similar to a C4 on EventStore Cloud. 3....
Consider this test program with @eventstore/db-client 3.4.0 and eventstore:21.10.7-bionic: ``` const { EventStoreDBClient, jsonEvent, } = require("@eventstore/db-client"); const client = EventStoreDBClient.connectionString('esdb://localhost:2113?tls=false') const streamName = "PerformanceTestNodeJsGrpc"; const numberOfEvents = 1000; function...
When creating a projection, the available options look like this: ``` export interface CreateProjectionOptions extends BaseOptions { /** * Enables tracking emitted streams. * @default false */ trackEmittedStreams?: boolean; }...
Lib version 3.3.1 Here is example ``` const { EventStoreDBClient, jsonEvent, START, FORWARDS } = require("@eventstore/db-client") var heapdump = require('heapdump') const client = new EventStoreDBClient( { endpoint: "localhost:2113", }, {...
Currently, batch append will keep it's connection open indefinitely. The connection should be closed if it hasn't been used for a specified length of time. Ref: https://github.com/EventStore/EventStore-Client-NodeJS/issues/283#issuecomment-1076499200
@tambeau commented on [Fri Nov 05 2021](https://github.com/EventStore/home/issues/640) Implementation of Node.js gRPC Projections API State - [ ] Get Query (Name, Config?) **blocked - Server Update Required** - [ ] Get...
After changing `readStream` and `readAll` methods to return the NodeJS stream instead of an array, it's impossible to get an array of events without using the handcrafted helper method or...
This issue is likely the same for individual stream subscriptions, but it isn't clear how to determine when a subscriber is caught up. **One use case**: Running a batch job...
Credentials tests are only testing reads, should be bulked up. https://github.com/EventStore/EventStore-Client-NodeJS/blob/master/src/__test__/connection/defaultCredentials.test.ts _Originally posted by @oskardudycz in https://github.com/EventStore/EventStore-Client-NodeJS/pull/229#discussion_r741862664_ [DEV-287](https://linear.app/eventstore/issue/DEV-287/bulk-up-credentials-tests)