It's been a while...
A quick status update and announcement.
I'm coming to RubyConf (https://www.rubyconf.org) the next month to talk about cables. Ping me if you're around and would like to chat)
I'm currently working on Ruby gem improvements (btw, I've added a GitHub dashboard a couple of months ago https://github.com/orgs/anycable/projects/1).
If you have some idea/suggestions/feature requests that you'd like to see in the next release–feel free to create an issue or ping me here!
I'm guessing it defaulted to private when you created it and needs to be explicitly made public
yep, looks like that; I didn't even know that there are privacy settings)
Yep, it's gonna bit a little bit different.
The mruby stuff is very interesting
That's the part I'd like to make shorter, since RubyConf is not so technical as RubyKaigi)
I'd like to present the new version of Ruby gem, some new benchmarks (including the bench for the upcoming ActionCable with new Rack API (rails/rails#33295)).
Probably, a little bit about our experiments with GraphQL subscriptions (and the way we make them work with AnyCable: https://github.com/Envek/graphql-anycable).
I haven't started working on slides yet)
Good news, everyone!
AnyCable gems (
anycable-rails) v0.6.0.rc1 are out!
We plan to push the RC on production this week, the final 0.6.0 release (with Docker, Heroku, Homebrew updates, and all the
anycable-go binaries) is planned for 15th of Nov.
Hi! Thanks for the feedback)
How difficult do you think it would be to have a seastar server to go along with the Go and Erlang servesr?
What do you mean by "go along"?
As I understand, Seastar is a kind of low-level web application framework; thus from AnyCable perspective it probably makes sense to build a WebSocket server on top of Seastar (as another one, not related to Go/Erlang implementations)
I realized that I’m not well aware of AnyCable production usage (though I see its mentioned from time to time is social media).
So, I’ve added a special GitHub issue to collect the feedback:
Please, share your story!
transmitsends message directly to the socket, while
broadcastuses pub/sub layer (Redis).
redis_channelsetting for both Ruby and WebSocket server (I guess,
anycable-go) is the same)
@/all Hey everyone!
Here is the survey for AnyCable users: https://evilmartians.typeform.com/to/W35uRm.
We want to learn more about you to make this piece of software better)
how do the steps below allow one to bypass that issue?
The described configuration assumes that you run both AnyCable RPC and AnyCable-Go on the same dyno. Thus HTTP2 traffic is running locally and is not affected by Heroku limitations.
Also, check the newer version of the docs: https://docs.anycable.io/#/heroku