Last week we hosted a webinar to show case some of the fun stuff in RavenDB. The recording is now available:
I started talking about this, and all of a sudden I got 45 minutes of pretty cool demo, even if I’m saying it myself.
In the video, I’m setting up RavenDB on a Raspberry PI, connect to it via the Python client API, connect it to the cloud and start working with widely distributed environment with bi-directional replication, ending up with using subscriptions to process data on the Raspberry PI that is coming from the cloud.
I would love your feedback on the video and the type of deployment that is outlined here.
I had a great time giving this talk, and I think it went really well.
You can watch the recording of the talk using the following link. I’ll also follow up tomorrow with more details about the printer that broke RavenDB, it seems to have hit a spot.
We are running another set of RavenDB workshops in London, Dallas and New York.
These are two days of deep dive into RavenDB. The workshop cover everything from how to talk to a RavenDB database to how to model your data, from how to setup a single node to building a geo-distributed cluster. It is also, at least in my opinion, a lot of fun.
Here are the details:
We’ll also be talking about some of the new features in 4.2 (and later) in the workshop.
The early bird pricing ends tomorrow.
"Select isn't broken" is an important bit of advice from the Pragmatic Programmer book. In most cases, you won't find bugs in your OS, programming languages or core libraries. It is almost always your code that is at fault. Except...
In this session, Oren will discuss how RavenDB has exposed numerous issues in the CoreCLR, the JIT and the underlying operating systems. Along the way, you'll learn deep debugging techniques and how to rule out your own code and pinpoint the actual underlying problem.
Over the weekend, I learned that Joe Armstrong has passed away. I have been thinking about through all of yesterday, because I have met Joe and had a few discussions with him, but I never had the chance to actually know him. Which is a shame, in a way, he changed my life.
One of the advantages of having a blog is that I can go back in time and trace things. In Sep 2007, I run into Joe for the first time. It was in the JAOO conference in Aarhus. I sat in his talk and was quite impressed. This is what I had to say at the time:
I was at the Erlang talk, which is quite probably the best one that will be here. Joe has created the language and wrote the book about it, so he certainly knows his stuff, and he is a Character with a capital C. I am not sure if it is a show or not, but it was amazingly amusing.
Bought the Erlang book, it is a weird language compare to those I know, but I really need to learn a new language this year, and Erlang gets me both functional and concurrent aspects for the "price" of one.
A couple of years later I was at the same conference and wrote:
I remember sitting at a session with Joe Armstrong talking about Erlang and finally getting things that were annoying just beyond my grasp.
Even since, whenever we were in the same conferences, I made sure to sit in his talk. He was an amazing speaker and I still carry with me his advice on system design and distributed architecture. I never really liked the Erlang syntax, but the concepts were very attractive to me. It took a while for this to percolate, but after reading some more about Erlang, I looked for an OSS project in Erlang that I could read, to actually grok what it is like to write in Erlang. I chose to read the CouchDB source code.
This was the first time that I really dove down into NoSQL and I remember running into all sort of things inside the CouchDB source code and thinking: “That isn’t how I would do it.” That code review ended up giving me so many ideas that I had to put them on paper (on keyboard, actually, I guess) and I wrote a whole series of blog posts on how to design a document database.
Just writing about it didn’t help, so I sat down and wrote some code. Some code turned into a lot of code, and that ended up being RavenDB.
And I can trace it all back to sitting in a conference room in JAOO, listening to Joe speak and being blown away.
Thank you, Joe.
I’m going to be in London at the beginning of June. I’ll be giving a keynote at Skills Matters as well as visiting some customers.
I have a half day and a full day slots available for consulting (RavenDB, databases and overall architecture). Drop me a line if you are interested.
I also should have an evening or two free is there is anyone who wants to sit over a beer and chat.
I just realized that this is my first blog post, it was published in April 1st, 2004.
I don’t really know what else to say, to be honest. I have been doing this blog for 15(!) years.
I’m going to be talking at CodeNode in London on June 3rd.
The topic of this talk is a few bugs that we found in the CoreCLR framework, the JIT and even the Operating System, how we tracked them down and put them down.
I have blogged about some of these in the past, and I’m looking forward to giving this talk. You can expect a talk that ranges between WinDBG walk throughs and rants about the memory model assumptions made on a different platform six years ago.