News for hackers. Stuff that matters.

Vishnevskiy

Re:How Discord Won on Monday October 19, 2020 @03:25PM (#24829903)
Who says we require it now ;)
Re:Discord Desktop App RCE on Monday October 19, 2020 @12:44AM (#24823395)
We only allow iframes for a few sites and this was one of them.
We found the name is not an issue as growth continues at a rapid pace.

We are already multiple times larger than Slack :)

This is how we will make money.

https://blog.discordapp.com/the-discord-store-beta-9a35596fd...

Aside from the money we already make from https://discordapp.com/nitro :)

Re:Why Discord Is Sticking with React Native on Thursday July 26, 2018 @09:35PM (#17622824)
Thanks!

And thank you for helping make Rust awesome.

Re:As Discord nears 100M users, safety concerns are heard on Thursday December 07, 2017 @10:46PM (#15876526)
Android, iOS? Do they use automatic detection or did they adjust the thresholds.
Re:As Discord nears 100M users, safety concerns are heard on Thursday December 07, 2017 @10:21PM (#15876443)
Is this only in our web client or also in our desktop client?
Re:How Discord Scaled Elixir to 5M Concurrent Users on Tuesday July 11, 2017 @11:36PM (#14749975)
We started with Elixir, some of our engineers have used Erlang prior though.
Re:How Discord Scaled Elixir to 5M Concurrent Users on Tuesday July 11, 2017 @11:34PM (#14749970)
We are currently in the process of testing ScyllaDB with double writes for our fixed data clusters. It is very scary to transition to something so new :)

Our message storage clusters have a very large set of data that keeps increasing and using Scylla without incremental repair will suck so we are waiting on that.

Re:How Discord Scaled Elixir to 5M Concurrent Users on Tuesday July 11, 2017 @11:33PM (#14749965)
You are 100% right that it is the best at what it does.

And thank you again with helping us with that bug :) we really appreciate it.

Re:How Discord Scaled Elixir to 5M Concurrent Users on Tuesday July 11, 2017 @07:11PM (#14748843)
:) np

We love Cassandra, and hate it at the same time.

Check out this nasty bug we got. https://issues.apache.org/jira/browse/CASSANDRA-13004

Re:How Discord Scaled Elixir to 5M Concurrent Users on Tuesday July 11, 2017 @06:36PM (#14748673)
The messages struggles have been sadly due to issues with Cassandra and GC pauses caused by bugs within it. We have been trying to work with the Cassandra developers to resolve these.

Voice issues should not be happening. Please contact our support with more information and we will gladly investigate.

What's funny is I got rejected from YC with Guildwork years ago. After flailing around trying to make it work I reflected on why it didn't work, Discord was the result. :)
Re:How Discord Stores Billions of Messages Using Cassandra on Friday January 20, 2017 @03:34AM (#13442426)
Cassandra has a snapshat command that creates a directory by symlinking files that hold data (this is safe cause Cassandra files are immutable). Then you just upload them to your backup storage. This is obviously for recovery scenarios that are catastrophic.

Normally though since the data is replicated on 3 nodes, you can technically loose a node completely and rebuild it from the other nodes.

Re:How Discord Stores Billions of Messages Using Cassandra on Friday January 20, 2017 @03:33AM (#13442422)
Update if exists, otherwise insert.
Re:How Discord Stores Billions of Messages Using Cassandra on Friday January 20, 2017 @12:13AM (#13441850)
This should not be the case, we strive for Discord be lightning fast at all times.

Please email me [email protected] I would love more details.

Re:How Discord Stores Billions of Messages Using Cassandra on Friday January 20, 2017 @12:11AM (#13441847)
The pricing model does not fit our needs, and that is even more locked in than the BigTable variant.
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @10:36PM (#13441575)
This post was about using Cassandra for message storage.

You are basically advocating for plugging 2 systems together, which out of the box don't provide elasticity. Or we could just use Cassandra. It is a simpler solution and Cassandra is not new tech. Aside from caching empty bucket information we have nothing sitting in front of Cassandra. It works great and the effort was minimal.

The Redis comment by jhgg was referring to our service which tracks read states for each user. We might write about that later, but it's not as interesting. The most interesting about that experience was reusing memory in Go to avoid thrashing the GC.

We care about seamless elasticity for our services which Redis doesn't provide out of the box except with Redis Cluster which does not seem to be wildly adopted and forces routing to clients.

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @09:46PM (#13441412)
The normal token system revokes on password change, if you want to revoke and have extra security we offer MFA login which has unique tokens per login. If security is of importance to you then use MFA.
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @09:37PM (#13441384)
We currently don't share exact metrics for all those stats, but we have shared a few press releases and blog posts which you can easily extrapolate from. :)
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @09:34PM (#13441365)
They did make the original and the core model is the same, but Cassandra in 2017 is quite different from what they open sourced in features, usability and stability.

I guess everyone makes their own tradeoffs though. This has been working wonderfully for us.

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @08:52PM (#13441173)
Last-write-wins is a semantic we are okay with for this data, and dealing with one of our conflicts is outlined the article.
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @08:08PM (#13440961)
Let me take a stab at that.

Riak is not a good model since its more a blob store and we wanted to simply range scan through messages rather than sharding blobs (Cassandra is REALLY good at this).

HBase would have been fine for this model, but the open source version of HBase has much lower adoption than Cassandra so that was a big factor. We also don't care about consistency and HBase is a CP database, we prefer AP for this use case. As far as using GCP's BigTable (HBase compat), we made this decision before we moved to GCP, but we are also not fans of using platform lock-in. While BigTable has the same API as HBase we would hate to go to an less widely adopted version where we have a hard time getting community support if we decided to leave GCP.

Hope that helps.

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @07:42PM (#13440840)
I am :) glad people remember me from FFXI haha

Add me on Discord if you ever wanna chat, Stanislav#7943

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @07:41PM (#13440836)
I sure am!

Add me on Discord if you wanna chat Stanislav#7943

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @06:11PM (#13440338)
We are larger than Slack
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @06:09PM (#13440328)
The problems that Jepsen found were centered around the "transactions" feature that Cassandra added. We don't use these and don't need them since we don't need 100% consistency and prefer availability (for example we read at quorum to trigger read repair, but downgrade to single node reads if we need to).

Also ScyllaDB is a new product and it would be crazy to start off with it. We plan to run a long-term double write experiment before we are comfortable with using it as a primary data store.

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @05:38PM (#13440131)
We have plans to make using temporary sessions in games a much better experience so look out for that in the future.
Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @05:27PM (#13440054)
We don't have an archive downloader, but you can use our API to scan over the history and save it.

https://discordapp.com/developers/docs/resources/channel

Re:How Discord Stores Billions of Messages Using Cassandra on Thursday January 19, 2017 @05:16PM (#13439960)
We make friends with owners of large public Discords and they had no problem with being included. The owner of that Discord even enjoyed reading the blog post.

You can also search past messages and the blog post ends with saying the follow-up will be about search. Search is not rolled out to everyone but will next week.

https://support.discordapp.com/hc/en-us/articles/11500046858...

Older »