You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/clients/tcp/dotnet/21.2/appending.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ static async Task Main()
83
83
84
84
## Transactions
85
85
86
-
You might perform multiple writes to KurrentDB as one transaction. However, the transaction can only append events to one stream. Transactions across multiple streams are not supported.
86
+
You might perform multiple writes to EventStoreDB as one transaction. However, the transaction can only append events to one stream. Transactions across multiple streams are not supported.
87
87
88
88
You can open a transaction by using the `StartTransactionAsync` method of the `IEventStoreConnection` instance. After you got the transaction instance, you can use it to append events. Finally, you can either commit or roll back the transaction.
89
89
@@ -182,7 +182,7 @@ If the optimistic concurrency check fails during appending, a `WrongExpectedVers
182
182
183
183
## Idempotence
184
184
185
-
If identical append operations occur, KurrentDB treats them in a way which makes it idempotent. If a append is treated in this manner, KurrentDB acknowledges it as successful, but duplicate events are not appended. The idempotence check is based on the `EventId` and `stream`. It is possible to reuse an `EventId` across streams whilst maintaining idempotence.
185
+
If identical append operations occur, EventStoreDB treats them in a way which makes it idempotent. If a append is treated in this manner, EventStoreDB acknowledges it as successful, but duplicate events are not appended. The idempotence check is based on the `EventId` and `stream`. It is possible to reuse an `EventId` across streams whilst maintaining idempotence.
186
186
187
187
The level of idempotence guarantee depends on whether the optimistic concurrency check is not disabled during appending (by passing `ExpectedVersion.Any` as the `expectedVersion` for the append).
Copy file name to clipboardExpand all lines: docs/clients/tcp/dotnet/21.2/connecting.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,21 +11,21 @@ Describe connecting to the single node and to the cluster.
11
11
12
12
Gossip seeds, using ip addresses and DNS.
13
13
14
-
The .NET Client API communicates with KurrentDB over TCP, using length-prefixed serialised protocol buffers. The API allows for reading and appending operations, as well as for subscriptions to individual event streams or all events appended.
14
+
The .NET Client API communicates with EventStoreDB over TCP, using length-prefixed serialised protocol buffers. The API allows for reading and appending operations, as well as for subscriptions to individual event streams or all events appended.
15
15
16
16
## EventStoreConnection
17
17
18
-
The `EventStoreConnection` class maintains a full-duplex connection between the client and the KurrentDB server. `EventStoreConnection` is thread-safe, and we recommend that you create one node per application.
18
+
The `EventStoreConnection` class maintains a full-duplex connection between the client and the EventStoreDB server. `EventStoreConnection` is thread-safe, and we recommend that you create one node per application.
19
19
20
-
KurrentDB handles all connections asynchronously, returning either a `Task` or a `Task<T>`.
20
+
EventStoreDB handles all connections asynchronously, returning either a `Task` or a `Task<T>`.
21
21
22
22
::: tip
23
23
To get maximum performance from a non-blocking connection, we recommend you use it asynchronously.
24
24
:::
25
25
26
26
## Quick start
27
27
28
-
The code below shows how to connect to an KurrentDB server, appends to a stream, and read back the events. For more detailed information, read the full pages for connecting to a server using [connection string](#connection-string) and [connection settings](#connection-settings), [reading events](reading.md) and [appending to a stream](appending.md)
28
+
The code below shows how to connect to an EventStoreDB server, appends to a stream, and read back the events. For more detailed information, read the full pages for connecting to a server using [connection string](#connection-string) and [connection settings](#connection-settings), [reading events](reading.md) and [appending to a stream](appending.md)
29
29
30
30
::: tabs
31
31
@tab JSON format event
@@ -42,7 +42,7 @@ We recommended using the JSON format for data and metadata.
42
42
43
43
Many of the `EventStoreConnection.Create` overloads accept a connection string that you can use to control settings of the connection. A benefit to having these as a connection string instead of using the fluent API is that you can change them between environments without recompiling (i.e. a single node in `dev` and a cluster in `production`).
44
44
45
-
For example, the following code will create a connection to an KurrentDB local node, and then open the connection:
45
+
For example, the following code will create a connection to an EventStoreDB local node, and then open the connection:
|`Create(string connectionString)`| Connects to KurrentDB with settings from connection string |
58
-
|`Create(string connectionString, ConnectionSettingsBuilder builder)`| Connects to KurrentDB by merging connection string settings with pre-populated builder for additional settings |
57
+
|`Create(string connectionString)`| Connects to EventStoreDB with settings from connection string |
58
+
|`Create(string connectionString, ConnectionSettingsBuilder builder)`| Connects to EventStoreDB by merging connection string settings with pre-populated builder for additional settings |
59
59
60
60
The connection string format should look familiar to those who have used connection strings in the past. It consists of a series of key/value pairs separated by semicolons.
61
61
@@ -156,12 +156,12 @@ Here are all available overloads for the `Create` methods of the `EventStoreConn
|`Create(ConnectionSettings connectionSettings)`| Connects to KurrentDB using specified settings |
160
-
|`Create(Uri uri)`| Connects to KurrentDB (see URIs below) with default settings |
161
-
|`Create(ConnectionSettings connectionSettings, Uri uri)`| Connects to KurrentDB (see URIs below) with specified settings |
162
-
|`Create(string connectionString)`| Connects to KurrentDB with settings from connection string |
163
-
|`Create(string connectionString, ConnectionSettingsBuilder builder)`| Connects to KurrentDB by merging connection string settings with pre-populated builder for additional settings |
164
-
|`Create(ConnectionSettings connectionSettings, IEndPointDiscover endPointDiscover)`| Connects to an KurrentDB cluster with custom settings. |
159
+
|`Create(ConnectionSettings connectionSettings)`| Connects to EventStoreDB using specified settings |
160
+
|`Create(Uri uri)`| Connects to EventStoreDB (see URIs below) with default settings |
161
+
|`Create(ConnectionSettings connectionSettings, Uri uri)`| Connects to EventStoreDB (see URIs below) with specified settings |
162
+
|`Create(string connectionString)`| Connects to EventStoreDB with settings from connection string |
163
+
|`Create(string connectionString, ConnectionSettingsBuilder builder)`| Connects to EventStoreDB by merging connection string settings with pre-populated builder for additional settings |
164
+
|`Create(ConnectionSettings connectionSettings, IEndPointDiscover endPointDiscover)`| Connects to an EventStoreDB cluster with custom settings. |
165
165
166
166
::: tip
167
167
The connection returned by these methods is inactive. Use the `ConnectAsync()` method to establish a connection with the server.
@@ -174,7 +174,7 @@ The create methods support passing of a URI to the connection as opposed to pass
Where the port number points to the TCP port of the KurrentDB instance (1113 by default) or points to the manager gossip port for discovery purposes.
177
+
Where the port number points to the TCP port of the EventStoreDB instance (1113 by default) or points to the manager gossip port for discovery purposes.
178
178
179
179
With the URI based mechanism you can pass a DNS name and the client will resolve it. The client performs a blocking DNS call for single node. If you are worried about blocking DNS due to network issues etc., you should resolve the DNS yourself and pass in an IP address.
180
180
@@ -195,7 +195,7 @@ By default, information about connection, disconnection and errors are logged, h
195
195
196
196
### User credentials
197
197
198
-
KurrentDB supports [Access Control Lists](security.md#access-control-lists) that restrict permissions for a stream based on users and groups. `EventStoreConnection` allows you to supply credentials for each operation, however it is often more convenient to set default credentials for all operations on the connection.
198
+
EventStoreDB supports [Access Control Lists](security.md#access-control-lists) that restrict permissions for a stream based on users and groups. `EventStoreConnection` allows you to supply credentials for each operation, however it is often more convenient to set default credentials for all operations on the connection.
The .NET API and KurrentDB can communicate either over SSL or an unencrypted channel (by default).
213
+
The .NET API and EventStoreDB can communicate either over SSL or an unencrypted channel (by default).
214
214
215
-
To configure the client-side of the SSL connection, use the builder method below. For more information on setting up the server end of the KurrentDB for SSL, see [SSL Setup](security.md).
215
+
To configure the client-side of the SSL connection, use the builder method below. For more information on setting up the server end of the EventStoreDB for SSL, see [SSL Setup](security.md).
Uses an SSL-encrypted connection where `targetHost` is the name specified on the SSL certificate installed on the server, and `validateServer` controls whether the connection validates the server certificate.
222
222
223
223
::: warning
224
-
In production systems where credentials are sent from the client to KurrentDB, you should always use SSL encryption and you should set `validateServer` to `true`.
224
+
In production systems where credentials are sent from the client to EventStoreDB, you should always use SSL encryption and you should set `validateServer` to `true`.
225
225
:::
226
226
227
227
### Node preference
228
228
229
-
When connecting to an KurrentDB HA cluster you can specify that operations are performed on any node, or only on the node that is the master.
229
+
When connecting to an EventStoreDB HA cluster you can specify that operations are performed on any node, or only on the node that is the master.
Copy file name to clipboardExpand all lines: docs/clients/tcp/dotnet/21.2/embedded.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,10 +9,10 @@ sitemap:
9
9
10
10
## EmbeddedVNodeBuilder
11
11
12
-
The `EmbeddedVNodeBuilder` class sets up and builds an KurrentDB node. You can configure your node through methods provided by the `EmbeddedVNodeBuilder` class.
12
+
The `EmbeddedVNodeBuilder` class sets up and builds an EventStoreDB node. You can configure your node through methods provided by the `EmbeddedVNodeBuilder` class.
13
13
14
14
::: tip
15
-
The builder used for the `EmbeddedVNodeBuilder` is the same KurrentDB uses internally to create the `ClusterNode`, see _EventStore.ClusterNode.Program.cs_ for more examples on how to use it.
15
+
The builder used for the `EmbeddedVNodeBuilder` is the same EventStoreDB uses internally to create the `ClusterNode`, see _EventStore.ClusterNode.Program.cs_ for more examples on how to use it.
16
16
:::
17
17
18
18
## Building a node
@@ -61,7 +61,7 @@ When running an embedded cluster, the task returned by `StartAndWaitUntilReady()
61
61
62
62
## Connecting to an embedded node
63
63
64
-
You can connect to an embedded KurrentDB node with the `EmbeddedEventStoreConnection` class. Calling `EmbeddedEventStoreConnection.Create(ClusterVNode)` returns an `IEventStoreConnection` configured to connect to your embedded node. From there you can use the connection as normal in the .NET Client.
64
+
You can connect to an embedded EventStoreDB node with the `EmbeddedEventStoreConnection` class. Calling `EmbeddedEventStoreConnection.Create(ClusterVNode)` returns an `IEventStoreConnection` configured to connect to your embedded node. From there you can use the connection as normal in the .NET Client.
0 commit comments