I was unfamiliar with Redpanda, and now I know and trust it. Whatever marketing budget Redpanda spent to get a Jepsen report was well worth it.
Jepsen: Redpanda 21.10.1
41–50 of 61 posts
Re: Jepsen: Redpanda 21.10.1
#42> A KafkaConsumer, by contrast, will happily connect to a jar of applesauce14 and return successful, empty result sets for every call to consumer.poll. This makes it surprisingly difficult to tell the difference between “everything is fine and I’m up to date” versus “the cluster is on fire”, and led to significant confusion in our tests. This tickled my funny bone. Never expected humor in a Jepsen writeup. Kudos!
Wait until you find out why it's called “Jepson”
Re: Jepsen: Redpanda 21.10.1
#43Re: Jepsen: Redpanda 21.10.1
#44Also I wanted to say to redpanda: I was on the fence but now I’m convinced. Will definitely be deploying on my next project, which has already kicked off. I only wish I could run it natively on MacOS instead of requiring docker.
Re: Jepsen: Redpanda 21.10.1
#45Earlier quoted context omitted.
Wait until you find out why it's called “Jepson”
please tell me it has something to do with carly jepsens song "call me maybe"
Changing "call me" to "call me maybe."
If you will.
Re: Jepsen: Redpanda 21.10.1
#46Re: Jepsen: Redpanda 21.10.1
#47Earlier quoted context omitted.
Wait until you find out why it's called “Jepson”
please tell me it has something to do with carly jepsens song "call me maybe"
Re: Jepsen: Redpanda 21.10.1
#48This isn't anything against Redpanda, but I'm always amazed how badly all these distributed databases do in Jepsen. What would one use them for in practice, which wouldn't be better suitable by a (the thing I've used), say postgresql and streaming replication in case the server goes down? (I'm not suggesting there isn't a good application, just I'm not knowledgeable enough to know of one).
There's a lot of different ways to answer this, but I think about it as a different architectural paradigm. Yes you can do stream-ish things with Postgres but at some level of scale you'd be putting a square peg in a round hole. What opened my eyes to this world is this post from Martin Kleppman on turning the database inside out: https://martin.kleppmann.com/2015/03/04/turning-the-database...
Databases are only as bad as the filesystem wrt being mutable, but since we do expect them to be a "better filesystem" it's surprising we let them get away with losing data. IMO beyond transactions you should just be able to unwind any writes to a SQL database, including deletes, for at least a day.
But if you ask Alan Kay he'd say all programs should have an explicit concept of time and be able to operate on the past and future state of everything.
Re: Jepsen: Redpanda 21.10.1
#49I was unfamiliar with Redpanda, and now I know and trust it. Whatever marketing budget Redpanda spent to get a Jepsen report was well worth it.
I happened to know RedPanda founder back in the days he was at Concord.io (as a founder and a main dev). The level of obsession with performance and optimization of this guy was insane. He's not only extremelly skilled with C++, but also very passionate about rethinking large and complex systems and rebuilding them to enable 10-100x speed improvements. It's like his personal hobby – take a piece of software everyone…
Re: Jepsen: Redpanda 21.10.1
#50I was unfamiliar with Redpanda, and now I know and trust it. Whatever marketing budget Redpanda spent to get a Jepsen report was well worth it.
I happened to know RedPanda founder back in the days he was at Concord.io (as a founder and a main dev). The level of obsession with performance and optimization of this guy was insane. He's not only extremelly skilled with C++, but also very passionate about rethinking large and complex systems and rebuilding them to enable 10-100x speed improvements. It's like his personal hobby – take a piece of software everyone…