9 years! A whole new world.
I have been missing you! Indeed, last year, I have not been able to publish my anniversary blog post as Iâm used to do every year since I joined Elastic 9 years ago. That was for a technical reason actually. I was using a old and not updated blogging platform and it took me a looooong time before I was able to invest time to switch everything to Hugo. So here we go! This year celebrates my 9 years anniversary at elastic but also a new blogging system.
7 years! Finding the right balance
What a ride! 10 employees to around 2000 now. As I imagined 8 years ago, I still think that Elasticsearch (the product) and elastic (the company) are successful. Becoming a public company did not change a lot my daily activities. Iâm still on the road meeting/building the community, specifically in France and making sure people are sharing the same love that we have internally for the products we are building. Iâd like this year to focus this anniversary blog post on some items:
5 years. What a milestone!
What a milestone! Can you imagine how changed the company in the last 5 years? From 10 employees when I joined to more than 700 now! If you want to read again my story, itâs there: 2013: Once upon a time⊠2014: Once upon a time: a year later⊠2015: Once upon a time: Make your dreams come true 2016: 3 years! Time flies! 2017: 4 years at elastic! Before speaking about what happened the last 5 years for me, letâs modify a bit the script I wrote last year.
4 years at elastic!
This post is starting to become a long series đ Yeah! Thatâs amazing! I just spent 4 years working at elastic and Iâm starting my happy 5th year! If you want to read again my story, itâs there: 2013: Once upon a time⊠2014: Once upon a time: a year later⊠2015: Once upon a time: Make your dreams come true 2016: 3 years! Time flies! This year, I will celebrate this by writing a new tutorialâŠ
3 years! Time flies!
3 years! Can you imagine that? Already 3 years spent working at elastic? Time flies! 2015 has been an uncommon year for me. Not because Marty Mc Fly and Doc Emmett Brown finally arrived⊠Not because, Han Solo, Leia and friends were finally back again⊠But for technical and also personal reasons. On a personal side, I had to deal with two major issues which cause some slow down in my professional activities. I had to cancel some conferences for instance.
Once upon a time: Make your dreams come true
Oh wait! Already 2 years spent working for Elasticsearch? Time flies! After the first year, I wrote that I did 58 talks in 4 countries, 37 towns for about 18 000 kilometers traveled. I was pretty sure that things would continue to grow. This year, I spoke 78 times! Around 2 talks per week! I did around 48 000 kilometers. 8 000 km more than the earthâs circumference! I still canât believe it⊠12 countries. And no need to say that I love giving talks and sharing my enthusiasm about Elasticsearch!
Once upon a time: a year later...
I joined Elasticsearch Inc one year ago. Those were pretty exciting days! But now⊠Itâs more than that! Really! You could think that after one year, my motivation would start to decrease. I have the total opposite feeling. Still excited by my job, by the company and by the project, but most of all by the amazing team Iâm lucky to work with! Everyone is different and each of us adds different value to Elasticsearch. Personally, I learn a lot from my co-workers.
Once upon a time...
Once upon a time⊠In fact 2 years ago, I was looking for a way to make Hibernate search distributed on multiple nodes. My first idea was to store indexes in a single database shared by my nodes. Yes, itâs a stupid idea in term of performances but I would like to try to build it. Digging for source code, I came to the JdbcDirectory class from the compass project. And I saw on the compass front page something talking about the future of Compass and Elasticsearch.
Il était une fois : un conte de fées élastique !
Il Ă©tait une fois⊠En fait, il y a 2 ans, je cherchais un moyen pour distribuer Hibernate search sur plusieurs noeuds. Ma premiĂšre idĂ©e Ă©tait de stocker les index dans une base de donnĂ©es partagĂ©e par les diffĂ©rents noeuds. Oui ! Il sâagit dâune idĂ©e stupide en terme de performances, mais jâavais envie dâessayer et de construire ce modĂšle. AprĂšs avoir cherchĂ© du code source, je suis finalement tombĂ© sur la classe JdbcDirectory du projet Compass.