11–20 of 20 posts
Earlier quoted context omitted.
Wait until you hear about "fractal storage" where every value in a table is a blob that contains a SQLite database, which in turn has blobs which contain SQLite databases, until it's turtles all the way down.
My God, it's full of stars. This is a joke, right? Please?
It's always interesting to observe my bad developer practices (such as stuffing JSON in SQL table columns) become flexible "architectural patterns" for building "schema-free, scalable data storage".
Its not storage friendly but it is what I believe to be a valid use case.
It's always interesting to observe my bad developer practices (such as stuffing JSON in SQL table columns) become flexible "architectural patterns" for building "schema-free, scalable data storage".
I'm flattered it's getting so much attention (I like having my ideas spread!), although there's one thing that confuses me. I've never heard of Hakka Labs, nor did I post the talk, video, or my bio on their site (although their treatment sure looks like I did) -- as far as I can tell, they grabbed it from the site of the SFRails Meetup at which I gave it and posted it online. I'm grateful for the exposure, but some notification or clear notice that I'm not affiliated with Hakka Labs (whatever/whoever they are) would have been nice.
It's always interesting to observe my bad developer practices (such as stuffing JSON in SQL table columns) become flexible "architectural patterns" for building "schema-free, scalable data storage".
My own experience is that there's actually more data than you'd expect that can fit into this model. On the other hand, I am absolutely not pushing this as a panacea: if you don't really know what you're doing, tossing JSON in a RDBMS is probably a really, really bad idea. After all, that's part of the talk -- to discuss when it's a good idea and when it isn't.
(I personally think the low-card tables part of the talk -- http://github.com/ageweke/low_card_tables -- is the most interesting idea.)
It's always interesting to observe my bad developer practices (such as stuffing JSON in SQL table columns) become flexible "architectural patterns" for building "schema-free, scalable data storage".
If you're working with a 3rd party api and want to store their response, it's waaay simpler to just stuff their response into a json blob, add a couple indexes if needed, and go on with life. (as opposed to making 30 tables to store all the data in a normalized format and writing the sql or configuring the orm to deal with that data)
Thanks for posting this. For what it's worth, I'm the author of this talk and the one pictured in the video. I'm flattered it's getting so much attention (I like having my ideas spread!), although there's one thing that confuses me. I've never heard of Hakka Labs, nor did I post the talk, video, or my bio on their site (although their treatment sure looks like I did) -- as far as I can tell, they grabbed it from the…
Thanks for posting this. For what it's worth, I'm the author of this talk and the one pictured in the video. I'm flattered it's getting so much attention (I like having my ideas spread!), although there's one thing that confuses me. I've never heard of Hakka Labs, nor did I post the talk, video, or my bio on their site (although their treatment sure looks like I did) -- as far as I can tell, they grabbed it from the…
Hi Andrew, I'm the founder of Hakka Labs. We had permission from the SFRails meetup orgs to record/post the talk, but I honestly apologize if this was unknown to you. We don't consider this 'our' content in any way, and we're happy to make it freely available for the benefit of engineers everywhere.
To me, http://www.hakkalabs.co/ looks a great deal like a blog. When I see a blog -- particularly with a name and photo of the author on an article -- I naturally assume that author either created that content specifically for that blog, or authorized/contributed that content specifically to that blog. If that's not the case, I think the blog needs to make it very clear that they are republishing content taken from elsewhere, without the author's knowledge. There's nothing wrong with that (assuming you have permission); it's just about making it clear that that is what's actually happening.
(Underneath, it's about the perception that I am somehow "contributing to" or "endorsing" Hakka Labs by posting content I created there. I'm not saying anything bad about Hakka Labs at all -- I simply don't know enough to judge either way! -- but IMHO it's not cool to create that perception without the author's knowledge. It'd be like a startup GitHub clone suddenly hosting my open-source code under an 'ageweke' account with my name and photo: while they absolutely have every right to do that according to the licenses involved, it gives the perception that I'm a user of their site and uploaded my code there...when, in fact, I've never heard of them before.)
Anyway, don't want to derail this technical discussion any further; feel free to reach out to me directly over email if you want to chat about anything else. You certainly have my email address. ;)