text stringlengths 0 1.82k |
|---|
**Carlisia Thompson:** Yes, exactly. |
**Erik St. Martin:** So we were actually talking about that a little bit this morning, because we know that Iron.io was a Ruby shot prior. How much Ruby is still left? |
**Travis Reeder:** There are still some bits and pieces that are in Ruby, typically the things that don't need to perform really well, and I just kind of haven't parted with them yet. To be honest, I'm still a Ruby fan. If I'm writing something that doesn't need to perform and won't be used by a lot of people, I'll sti... |
**Erik St. Martin:** I tell people that too, Ruby I think still has a special place in my heart. I love the way it reads, and stuff like that. For throwing together quick CRUD apps, you can't beat it. I can take Rails and I can throw together an admin area in a weekend, you know? And especially for prototyping. And alt... |
**Travis Reeder:** Right. |
**Carlisia Thompson:** Yes, I think when you write in Ruby and Ruby on Rails - I do it still, and it starts becoming a little bit problematic when it just grows and then you don't know what to do with it, so you start to think about Micro services, and maybe moving parts of your app that need to be more performant into... |
**Erik St. Martin:** My thought on Ruby these days is pretty similar to my thought on Java. It's not that I don't like the languages, I don't like the way people write the language. Ruby and Rails have been great, but these huge monolithic coupled together things because people just throw it together because they can, ... |
**Carlisia Thompson:** Yeah. And this question that you asked, Erik, reminded me of the question we were throwing around last week about whether we optimize for performance, and I think Travis should be the expert here - I am wondering, Travis, how do you plan for performance loads that you update in the future? How mu... |
**Travis Reeder:** It's impossible to predict, right? We didn't know what we would need upfront, that's why we went from Ruby and had to switch to Go. But nowadays we do have a better idea of what we need, and we just always try to push the limit. There is a recent blog post on our blog.iron.io about getting a million ... |
**Erik St. Martin:** Plus it's just cool |
**Travis Reeder:** It's cool, yeah. It's cool when you get those commas. |
**Brian Ketelsen:** Nothing makes us happier than good benchmarks. |
**Travis Reeder:** Yes, exactly. But that wasn't just Go. A lot of that is due to the database we chose, and the underlying technologies. We're actually using RocksDB under the hood. |
**Erik St. Martin:** Rocks is a really interesting project. |
**Brian Ketelsen:** Yeah, Rocks is awesome. |
**Erik St. Martin:** And CockroachDB is written on top of RocksDB, too. It basically is implementing some of Google Spanners paper, mixed with some other stuff, but that's all in Go, and then their file system layer is done with RocksDB. |
**Travis Reeder:** Yeah, I like that Cockroach project, I don't know where it's at now; it was pretty early last time I checked, but we basically did the same thing for IronMQ - we took Rocks as the persistence layer, which is super fast. It's nice for a queue too, because all the data is sorted; it kind of worked out ... |
**Erik St. Martin:** Did you end up using Raft for your consensus protocol? |
**Travis Reeder:** Well, I wasn't really on the IronMQ team in this kind of upgrade, but we were using something and I believe it is Raft. |
**Erik St. Martin:** And nobody wants to implement the other ones. \[laughter\] |
**Travis Reeder:** Yeah, yeah. |
**Erik St. Martin:** I remember the first time I saw the Raft paper; I was like, "Ten papers, that's it? No, this can't be right for a distributed consensus protocol? |
**Brian Ketelsen:** This is actually the paper consensus for mortals. |
**Erik St. Martin:** Yeah, that's right. The title was something like that, wasn't it? Alright, so let's talk about some interesting Go projects. Brian has this whole thing where he goes to sleep and he downloads all the interesting GitHub projects for Go, and then he just spews them out to me in the morning. |
**Brian Ketelsen:** It's how I get myself to sleep tonight: browsing the latest commits to Go projects. |
**Erik St. Martin:** And I hope that he curates it first, because I don't have that kind of time. |
**Brian Ketelsen:** I do, I only share the interesting ones. The first one today I saw a couple months ago and it was just in its beginnings, but it looks like it's getting pretty nice - there is an Oauth2 server, written by Richard Knop. It's called go-oauth2-server, and it looks like it's getting pretty solid in term... |
**Carlisia Thompson:** It has wonderful documentation. |
**Brian Ketelsen:** It does, some of the best I've ever seen for an Oauth server. |
**Carlisia Thompson:** Amazing. |
**Brian Ketelsen:** I agree. |
**Erik St. Martin:** For an Oauth2? \[laughter\] |
**Carlisia Thompson:** There are so many... |
**Erik St. Martin:** Speaking of Cockroach again, that is probably one of the best-documented projects I've ever seen, too. |
**Brian Ketelsen:** Oh, agreed. |
**Erik St. Martin:** That's just beautiful, so well documented. And the C++ code was pretty good, too. I don't think I've ever seen C++ look like that. |
**Brian Ketelsen:** Readable? |
**Erik St. Martin:** What is this weird language? Oh wait, this is C++. |
**Brian Ketelsen:** It's really C++? Alright, the second project I stumbled across a couple of weeks ago, and again, it's maturing to the point where it's starting to look really interesting, and that's Rqlite, which is the distributed SQLite. |
**Erik St. Martin:** Yeah, I've seen that, too. |
**Brian Ketelsen:** Adam's gonna tell us at some point that that's not how you pronounce SQLite. |
**Carlisia Thompson:** You're not pronouncing it right, it's SQLite. |
**Brian Ketelsen:** Well whatever it is, Rqlite is the Raft-enabled version of SQLite, and it allows you to have a distributed SQLite database, and that's all built in Go, it's distributed... Pretty slick stuff. It looks like it would be really high performance, so I'm kind of itching to test that one out. I might have... |
**Erik St. Martin:** What's the interface for that? They turned it into HTTP rather than interacting with like an actual SQLite adapter? |
**Brian Ketelsen:** Oauth, actually. You can query directly against the SQLiteDB on disk, and I think you're required to do all your data changes over the HTTP API, which actually just sends DDL. So the API is a really tiny JSON wrapper for DDL. |
**Erik St. Martin:** So the downside is just that you can't just use a normal SQLite adapter, you kind of have to develop a HTTP client to start your data, but still... It's really interesting though, because things like Raft, and etcd, and console has really enabled people to build their own distributed systems much m... |
**Brian Ketelsen:** Facebook did it with MongoDB. They took Mongo and stuffed Rocks underneath it, and have an extremely fast and fault-tolerant and high-performant database system. I think -- is it Charity Majors that heads that up? I can't remember, but anyway... Everybody's doing it, and it's cool. |
**Travis Reeder:** Anyone tried that Rocks backend from Mongo? |
**Brian Ketelsen:** I have not. |
**Erik St. Martin:** No... It was on my list, and... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.