brasetvik

14 ms·

91.
by brasetvik 12y ago
Great initiative. This one is a classic as well: What Goes Around Comes Around (Michael Stonebraker, Joseph M. Hellerstein) – http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.113.... "This paper provides a
92.
Optimizing Elasticsearch Searches(found.no)
90 points by brasetvik 12y ago|4 comments
93.
by brasetvik 12y ago
https://twitter.com/alexbrasetvik - mostly tidbits related to Elasticsearch and distributed systems, with a hint of skydiving.
94.
by brasetvik 12y ago
For local testing on Postgres where you don't care about database reliability, you can also speed things up a lot by setting `fsync = off` and `synchronous_commit = off`. (Never do that on a production database, of course!)
95.
Kibana 3.0 released(elasticsearch.org)
3 points by brasetvik 13y ago|0 comments
96.
by brasetvik 13y ago
Happy to help! I posted it since NoSQL was a hot topic in the 1.0 thread. If you're uncovering unknown unknowns, these can also be of interest: - https://www.found.no/foundation/elasticsearch-in-production/ -
97.
by brasetvik 13y ago
Thanks for the feedback! The point of that section is exactly that "NoSQL" (or to make things even more confusing "NOSQL" (Not only) doesn't have a very specific meaning. Some think it rules out ACID, other's d
98.
by brasetvik 13y ago
Hi, Nick. :) Indeed! That said, it's great that more people are picking up Elasticsearch for new exciting things. Elasticsearch has really pushed what constitutes a "search problem", and deserves lots of kudos for that! :)
99.
by brasetvik 13y ago
Sometimes, I actually find it easier to have more systems that do their job really well and sync things between them, rather than trying to get a single system to do everything. For example, Postgres lets you reason about integrity, atomici
100.
Elasticsearch as a NoSQL Database (2013)(found.no)
64 points by brasetvik 13y ago|3 comments
101.
by brasetvik 13y ago
I can't comment much on MongoDB, but I've written a bit things to keep in mind when considering Elasticsearch as a NoSQL store here: https://www.found.no/foundation/elasticsearch-as-nosql/
102.
by brasetvik 13y ago
You may not be using OpenBSD, but the same organization is behind OpenSSH. Imagine being without ssh, then go donate. :)
103.
by brasetvik 13y ago
You mean on the from side? Yes, just drop the existing index and create a unique index. You can do that within the same transaction. Postgres already requires the pointed to relation to have a unique index: => create table foo (id
104.
by brasetvik 13y ago
Hehe. Thanks for the vote of confidence. :) (Tip: You can auth with Github by clicking the octocat-icon, so you can save revisions of your query and get history through the gist. An often-missed feature I need to make more obvious. :)
105.
by brasetvik 13y ago
Oh hey. I'm the developer that's been working on Play. There's some more information about it here: https://www.found.no/foundation/presenting-play/ In summary, it's a preview - neither feature
106.
by brasetvik 13y ago
See also: What Goes Around Comes Around (Stonebraker and Hellerstein) http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.113.... That one's from the time where XML-databases were all the rage. Unfortunately,
107.
by brasetvik 13y ago
Have you looked into using Elasticsearch's date histograms as sources for Graphite-functions? Jordan Sissel wrote a short note about it over here: https://gist.github.com/jordansissel/3760225 That'll obviousl
108.
by brasetvik 13y ago
I wrote an article that covers some of this: http://www.found.no/foundation/elasticsearch-in-production/ It's a bit introductory on the memory-parts. One that goes in more detail on memory- and JVM-tuning is
109.
by brasetvik 13y ago
There's a book series "Translucent Databases" with a lot of interesting use cases, where the assumption is that an adversary has gained access to the entire database. I've only read the first edition, and it's some
110.
by brasetvik 13y ago
See also: http://www.matasano.com/articles/javascript-cryptography/
111.
by brasetvik 13y ago
I was more objecting the very marketing-y-and-not-very-truthy quote. That said, digging a bit more into Jottacloud does not make me any more likely to use the service, for anything I would be concerned to store at, say, Dropbox: Their FAQ i
112.
by brasetvik 13y ago
"In Norway, privacy stands firm like the mighty mountains of Jotunheimen.". Let's not flatter ourselves too much: http://no.wikipedia.org/wiki/Datalagringsdirektivet (in Norwegian, http://tr
113.
by brasetvik 13y ago
There is https://github.com/elasticsearch/elasticsearch-lang-javascri... Though, it is based on Rhino, not v8 – and it's not sandboxed.
114.
by brasetvik 13y ago
How was the evaluation process that led to using MongoDB in the first place? At some point you must have compared it to, say, Postgres – which is what the section before the summary hints to.
115.
by brasetvik 13y ago
NoNoJS.
116.
by brasetvik 13y ago
The NNN Stack: NoJS (Python, Twisted, Cyclone), NoNoSQL (PostgreSQL) and NoSQL (Elasticsearch).
117.
by brasetvik 13y ago
"The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair" – D. Adams.