@moshe is working on a Python binding, see #82 and https://github.com/moshe/asonic

Hello @valeriansaliou I have implemented a tiny go library for sonic https://github.com/expectedsh/go-sonic
Thanks you for your project !

Thank you so much, I'm adding it to the README right now.

Is there a Rust client library provided already? I imagine since the server is written in rust, it wouldn't be too difficult to put together a rust client.

If no one else has started working on it, I’d love to take on the Ruby client!

@kaspermeyer I confirm that to my knowledge no one has yet started working on the Ruby client, you can go for it 😄 Thanks!

Hey guys! I wrote a small php client library.
I am planning on using this to write a backend for Nextcloud's fulltextsearch framework.

@seijikun thanks! It's been added to the README in commit 777734c 👍

I have implemented a bulk feature in my library, maybe the official library (in nodejs) should have it ?
https://github.com/expectedsh/go-sonic/blob/master/sonic/ingester.go#L113

@alexisvisco thanks, looks neat. I'll think about it for the NodeJS library. At the network level, it's still the same so there's no (speed) optimizations involved w/ a bulk feature in the library, though it reduces the lines of code for users that need it.

In my implementation I have splitted the number of coroutines and assign a new connection to it (because in Go you can't read a connection by multiple coroutines and it's normal).

For example:
There is an array of 10 bulk values.
I decide to split into 2 coroutines (parallelRoutines field).
There is now 2 arrays of 5 elements that will be executed in parallel.

Each coroutines is independent so there is an optimisation because of the paralelization, you can speed up to 2 times faster in this case (if the sonic server can handle this traffic).
By the way I have executed a benchmark of this and it is positive, look at this 😄

@alexisvisco I see, you're able to increase the concurrency level at the library level. Sonic will definitely scale this better with your model, indeed. Depending on the number of cores of the machine it'll use CPU cores at their best as Sonic spawns an independent thread per Sonic Channel connection.

I have plans to add a worker pool to Sonic to handle the query + suggest commands. I've already made the protocol async-compatible for search mode (in advance), so any "worker pool" improvement in Sonic will not require any change in the protocol.

@alexisvisco just curious, in which context / for which project are you using Sonic, if so? What motivated you to build the Golang integration? (if that can be said publicly)

I'll probably have a go at making a native Rust client. Should make for a good learning experience!

@alexisvisco just curious, in which context / for which project are you using Sonic, if so? What motivated you to build the Golang integration? (if that can be said publicly)

@valeriansaliou Expected.sh is a 🇫🇷 container as a service, we want to build something awesome.

We wanted to use Sonic to ingest logs and be able to search them. However we noticed that it does not really fit because we would have wanted to be able to filter over time, and for now we can't with Sonic. We will keep an eye on sonic but we will rather use something else.

To be honest I have created the Go driver because our stack is in Go and I wanted to quickly know all of sonic. And also because the project looked cool 😎

Hi! I've created a Ruby client for Sonic - https://github.com/atipugin/sonic-ruby. There are some improvements to do, but it's already usable :)

Thanks @atipugin I've added it to the README 👍

@touhonoob and me have merged our libraries into his repository, so you can remove my repo from the README. 😃

@seijikun done in cfbd3ac

Hi,I found that the current java client is synchronous, so I wrote an asynchronous client using netty.https://github.com/alohaking/jsonic

@alohaking can you submit a PR where you add the link to your library in the README, below the other Java library? Thanks!

@alohaking just did it myself. Thanks!

Hmm I see that im late to the party :( https://github.com/OGKevin/go-sonic

#77 (comment)

The only thing is missing is proper client documentation, make sure the query length is checked to prevent overflow and actually implementing it in my own project.

You can still submit a PR to add your library to Sonic's README ;)

Hi, I made a Rust client sonic_client, using mio and channels.
There is a question though, is QUERY and SUGGEST share the same id pool? Do I need make 2 maps for them or just one.

Hi there! Thanks a ton, adding it to README now!

Regarding your question, yes, they can share the same ID pool as all async events are routed on the same TCP channel (in search mode).