51–60 of 73 posts
I'm interested in the http://seastar.io/ networking library that the Scylla guys built. Looks like it runs on DPDK and might be a nice way to do user mode networking. Anyone tried using it in other projects?
I've also been interested in this project. Several years ago, I was toying with the idea of building a Kafka-compatible broker implementation with it. Although I didn't get very far, it's a very powerful and well-designed framework.
Earlier quoted context omitted.
Agree it's annoying (I'm one of the co-founders) but it's the minimal 'eval' to make sure users succeed to maximize the value from their downloads. We mainly push them to slack and to share monitoring and logs with us, until they get to prod
It also means we can't automate installation of ScyllaDB.
Also Scylla provides non-gated access for AWS users with ready-to-consume AMIs
Earlier quoted context omitted.
It also means we can't automate installation of ScyllaDB.
Most of our users automate it. When you register, you are given access to the repository file for your preferred distribution. Once you have the repo, you can just apt-get it into every one of your nodes. Also Scylla provides non-gated access for AWS users with ready-to-consume AMIs
Anyone using this in production? Any thoughts or tips on how to adapt traditional MongoDB workflows to this?
Earlier quoted context omitted.
I've also been interested in this project. Several years ago, I was toying with the idea of building a Kafka-compatible broker implementation with it. Although I didn't get very far, it's a very powerful and well-designed framework.
i have a prototype of that same idea working w/ seastar.
They need to get rid of that email registration to download the software.
Why?
I know I only bother with these more annoying products after I've already tried and failed with the alternatives. Its not so much the few minutes dealing with registration and the other time working out if access to the private repositories are going to be a hassle with my environment and security policies, its the first sign that you are dealing with a company that is going to be a hassle.
So please leave up the registration forms, because it signals to me that I will be dealing aggressive sales departments, fine print and hidden expenses. And I'm only going to do that when I've exhausted my alternatives. Maybe it isn't true, but its what I've come to believe over the last few decades, and I'm not the loser in this scenario since I just investigate the easier to deal with solutions first. And not much point continuing if I find something good enough and free, which is why I'm currently migrating my old DSE clusters to new hardware and Apache Cassandra 3.11 despite my poor experiences with older versions (I was pleasantly surprised with 3.11 and look forward to seeing 4.0).
Earlier quoted context omitted.
Why?
Agree it's annoying (I'm one of the co-founders) but it's the minimal 'eval' to make sure users succeed to maximize the value from their downloads. We mainly push them to slack and to share monitoring and logs with us, until they get to prod
Get ScyllaCloud barrier to entry a bit lower. $200/mo is too much for tinkering. Even better if there is an autoscaling option available.
Get ScyllaCloud barrier to entry a bit lower. $200/mo is too much for tinkering. Even better if there is an autoscaling option available.
It certainly is pricey for tinkering, but it requires a decent chunk of block storage and I was shocked how expensive that is when I looked the other day. It unlikely to be news to most, but I've been on private cloud and DCs for a long time and it seems everyone is charging huge amounts of money if you need large filesystems; not even slow but cheap options. Maybe Scylla needs to be backed by S3 rather than XFS :)
Awesome. Can't wait for the Amazon hosted version.