This Blog Has Moved!

Right, so yes, five years ago I moved to github pages, and never bothered to redirect any of these pages there. Now I've moved on from there, and... Finally I am using my real domain, trishagee.com . My blog is now at trishagee.com/blog .  See you there!
Post a Comment

Sevilla MUG, first event


Last night was the inaugural meeting of the Sevilla MongoDN User Group.  An event organised with just over 48 hours notice, in a city where I don't speak the language and where even my best-connected contacts aren't sure they're fully plugged in to the tech scene.

I'll admit, I had some reservations:

  • a lightning talk? Will people come all that way for beer and 15 minutes of presentation?
  • in English? Whilst I'm desperately learning Spanish to get closer to presenting in Spanish, at this point I'm just not ready and have to hope people want to listen to me ramble in a foreign language
  • a MUG? Are people interested in joining a group that's solely focussed on one technology, a technology that might not have adoption here or even interest?
  • two days notice?  Are you kidding?  I know people here like to figure out their plans at the last minute, but surely this is shooting ourselves in the foot before we even start.


And then last night...  The people... they came.  On time.  And with their interesting stories and their varied backgrounds.  They listened, they asked questions, they wanted more.


What a great event.  What an awesome city.

I can't wait for next month.


(Slides here, with usual caveats of them being pretty pointless on their own)

Comments

  1. Unknown31 January 2014 at 07:23

    Hi Trisha,

    at this moment is available a group, MUB( a assume this mean: MongoDB Users Group) ?,
    are there some video records for this sessions ?

    Thanks
    Sorin.

    ReplyDelete
    Replies
    1. Trisha31 January 2014 at 09:21

      Yes, MUG = MongoDB User Group

      We probably won't video the sessions because there are too many obstacles to overcome. However, you can see webinars and talks about MongoDB here: http://www.mongodb.com/presentations. And Martin Fowler has an intro to NoSQL here: http://www.youtube.com/watch?v=qI_g07C_Q5I.

      The aim of these sessions is not so much to teach (i.e. via the talks) but to meet other professionals nearby who you can talk to. That's hard to do via video, although if you're a Java person we're trying to achieve this via the vJUG: http://www.meetup.com/virtualJUG/

      Delete
  2. Unknown2 February 2014 at 20:21

    Thanks Trisha.

    ReplyDelete

Post a Comment

Comments have been disabled since this blog is no longer active.

Popular posts from this blog

Dissecting the Disruptor: What's so special about a ring buffer?

Image
Recently we open sourced the LMAX Disruptor , the key to what makes our exchange so fast.  Why did we open source it?  Well, we've realised that conventional wisdom around high performance programming is... a bit wrong. We've come up with a better, faster way to share data between threads, and it would be selfish not to share it with the world.  Plus it makes us look dead clever. On the site you can download a technical article explaining what the Disruptor is and why it's so clever and fast.  I even get a writing credit on it, which is gratifying when all I really did is insert commas and re-phrase sentences I didn't understand. However I find the whole thing a bit much to digest all at once, so I'm going to explain it in smaller pieces, as suits my  NADD audience. First up - the ring buffer.  Initially I was under the impression the Disruptor was just the ring buffer.  But I've come to realise that while this data structure is at the heart of the patte
Read more

Dissecting the Disruptor: Writing to the ring buffer

Image
This is the missing piece in the end-to-end view of the Disruptor.  Brace yourselves, it's quite long.  But I decided to keep it in a single blog so you could have the context in one place. The important areas are: not wrapping the ring; informing the consumers; batching for producers; and how multiple producers work. ProducerBarriers The Disruptor code has interfaces and helper classes for the Consumer s, but there's no interface for your producer, the thing that writes to the ring buffer.  That's because nothing else needs to access your producer, only you need to know about it.  However, like the consuming side, a ProducerBarrier is created by the ring buffer and your producer will use this to write to it. Writing to the ring buffer involves a two-phase commit.  First, your producer has to claim the next slot on the buffer.  Then, when the producer has finished writing to the slot, it will call commit on the ProducerBarrier . So let's look at the first bi
Read more

Dissecting the Disruptor: Why it's so fast (part one) - Locks Are Bad

Image
Martin Fowler has written a really good article describing not only the Disruptor , but also how it fits into the architecture at LMAX .  This gives some of the context that has been missing so far, but the most frequently asked question is still "What is the Disruptor?". I'm working up to answering that.  I'm currently on question number two: "Why is it so fast?". These questions do go hand in hand, however, because I can't talk about why it's fast without saying what it does, and I can't talk about what it is without saying why it is that way. So I'm trapped in a circular dependency.  A circular dependency of blogging. To break the dependency, I'm going to answer question one with the simplest answer, and with any luck I'll come back to it in a later post if it still needs explanation: the Disruptor is a way to pass information between threads. As a developer, already my alarm bells are going off because the word "th
Read more