Question: client stability

Hi Guys, we want to start using this client in our iOS app.

we are seeing the docs says it's not production-ready yet. does it related to the client also?
We are also waiting for auto-reconnect and routes features, do we have any estimation of when they will be implemented?

also, we are interested if there any company that uses any rsocket client on iOS in production?

Thank you in advance

[dnadoba]

Hi @liskov
Short answer is: the client is not ready for production.

Main topics which we need to work on before I think it is ready:

Closing a Connection and Connection State

It is currently not possible to really close a connection nor is it possible to even observe if a connection was closed by the server. We need to support gracefully closing all active streams (i.e. waiting until they have terminated) and non-gracefully e.g. when we no longer have a connection to the server because of keep-alive timeout. We have already started working on it.

Auto-Reconnection

After we can observe the connections state, we can implement auto-reconnect. We need to come up with a good algorithm which does not accidentally DDoS our own server infrastructure when it is down for a short period. For example a we could add a random delay so that not all clients reconnect at the same time.

Routing, Encoding/Decoding, Composite Metadata

We have already started working on a type-safe API to make it easy to define a Request. Some RSocket Extensions are not widely used and we still have some open questions about the specification which needs to be sorted out before we fell confident to settle on an API.

Production

We at Trade Republic are one of the main contributors to the Swift implementation because we want to use it in production but are currently not doing so. I'm not aware of any companies who are using it in production but I know some which are planing to do and some more who are evaluating it.

I can't commit on any timeframe. However, I would say this is roughly 2 weeks of work for a single engineer if the complexity of those topics does not increase significantly. As you can see in the commit history, we haven't worked on it for a couple of weeks because priorities have shifted. Nevertheless, we will not abandon this project and will continue to work on it. That being said, contributions are always welcome too 🙂.

[axiomaticSystem]

Hello! Are there any updates on @liskov question or is project in the same state?

[Strotsev]

Hello! Any updates here?

[nkristek]

Hi @Strotsev, unfortunately the state remains unchanged, but this does not mean, that development has stopped. More features and stability improvements are planned to be implemented, but it's hard to estimate how long this will take.

[Strotsev]

Hi, @nkristek!
Thank you for the reply.

I lead the department responsible for API support and improvements at dxFeed Solutions DE GmbH.
We have a strategic plan to use the RSocket implementation for our web and mobile solutions.
Right now it looks like a problem in case of connecting to iOS.

Could you give an advice in this case? Maybe some alternatives?
Interoping Kotlin implementation from Swift (iOS) or Cpp? Do you have end users who have production solutions for the specified stack (Web, iOS, Android)?

Here is my email: vstrotsev@devexperts.com
Thank you!

[Strotsev]

Hello! Are there any updates?

[sdack-cloud]

Eagerly waiting...

[niyaode]

Is there any progress now

[lizt8888888888]

Eagerly waiting...

[sdack-cloud]

Has the project stopped

[YohanSciubukgian]

Is Rsocket Swift viable for production in 2024?
More generally is RSocket using Server (Java), Web (TypeScript), IOS (Swift) & Android (Java) viable for production in 2024?