search

EventStore / EventStoreDB-Client-Dotnet-Legacy

1 stars 9 forks source link

Missing EventStore.Client.Embedded with version 20.6.1 #51

Open mh185277 opened 3 years ago

mh185277 commented 3 years ago

Please create new nuget package of EventStore.Client.Embedded version 20.6.1.

Martin

hayley-jean commented 3 years ago

Hi @mh185277

We're busy deciding on the future of the embedded client and are still working to resolve some issues with it. Would you mind telling us what you're currently using the embedded client for? For example, local development, testing, etc.

mh185277 commented 3 years ago

We want to run EventStore as a Windows service in production.

alexeyzimarev commented 3 years ago

Embedded client doesn't solve it. You can use nssm for that.

mk185147 commented 3 years ago

@alexeyzimarev Do you mean by "Embedded client doesn't solve it" that it isn't its primary purpose or that for some reason it isn't possible to use embedded client within a custom service properly?

I personaly see use of tools like nssm as not a nice thing to do (adds unnecesarry complexity), the best would be if EventStore was able to run as a service in first place which most likely can be done with a minimal change in EventStore source code (e.g. change EventStore.ClusterNode.exe to be Worker Service).

aaron-0 commented 3 years ago

@alexeyzimarev I posted this issue in the client library repo before seeing this thread: https://github.com/EventStore/EventStore-Client-Dotnet/issues/160

Background for why we use the embedded client:

We have a desktop application running on tablets that captures all data entered as domain events stored in EventStore running in embedded mode. The embedded EventStore is started and stopped as part of the net core application lifecycle, with a IHostedService that does the startup/shutdown.

Have you made a decision yet about the future of the embedded client? If the plan is to discontinue the embedded client is there a recommended way to achieve the same outcome?