Eventstore on Azure Container Services At work, Ryan shared this post about getting Eventstore running on Google Cloud Platform (GCP) to try out on Azure. Now for those of you who don’t want to read the entire other blog post, what it talks about is setting up a Eventstore cluster in two ways Cluster using Pod local storage - where if the pod goes down, you lose all data and when Kubernetes brings up another pod, it will have to catch up.
What? I have a couple of machines at home that I would like to be able to access remotely. Now, in the past, the way I’ve done this is: Setup Dynamic DNS on my router - so that home.rraghur.in will resolve to my router. Setup Port forwarding on the router to map an incoming port to port 22 of each internal machine that I want to access remotely.
Usually when researching a topic, I end up with a lot of tabs open in firefox - usually grouped by topic in 3 to 4 windows with 7 to 15 tabs in each - so we’re talking rougly 30 - 40 tabs at a time. With that many tabs, it’s just too slow to switch tabs with the mouse. First you have to Alt-Tab to the right window, then eyeball the right tab within the window (which is problematic if you have more than a handful of tabs that window titles don’t provide enough info)
In my previous post, I talked about microservices trade offs and how you need to be aware of them to navigate the waters. I also touched upon how we went about it successfully. In this post, I’ll go over some of the questions to pose to yourself/your team from an engineering/infrastructure standpoint as you embark on your microservices journey. Questions It helps to try and answer some of the questions below.
My photo from 2013 got a 100k views. This is from Bheemeshwari Nature and Adventure camp. If you’re in Bangalore, take the time to visit this place for a day or two - it’s just a 2 hour drive and totally worth it. Best time of the year’s after the monsoons in August/September when the river’s in full spate. Fond memories!
Everyone wants them, many claim to have used them with success, few in reality have done it right and a minuscule percentage understand the trade offs involved. They’re all the rage these days - if you don’t have a 'Microservices architecture' then someone higher on the totem pole is bound to pontificate that the approach is outdated/legacy. :) Of late, I’ve come across customers & teams where there’s a rush to 'do microservices' and I’ve spent a good amount of time laying out the trade offs and helping them evaluate their own readiness (or lack of it).
Getting a working cross platform experience with Git for Windows, MSYS git and Linux just wants me to jump off a cliff!