Exploring NATS, K8s, Distributed Systems, Prometheus, Grafana, Workflow and container orchestration.

Continuing my journey as a Go developer I started with a PoC on Apache Pulsar, I learned its internal, helped the team to move it to production, contributed to Pulsar's doc, found an issue in their client library and suggested a feature. My next task was to build a core back-end component in Go that would power the UserIQ's dashboard for hundred of accounts having thousands of users in near real time. I gained skills in benchmarking, profiling, optimizing code for performance, finding memory leaks and so much more. Learning from my failures, I was able to optimize this core library to return a response within 5ms(and yes, db calls were involved as well).The next interesting thing was to build a bunch of services around Pulsar and here came my favorite part: concurrency. I love Go's concurrency model and it's ease of use to write concurrent code in no time. Exploiting channels felt so good(well, I ran into deadlocks multiple times). I admire the beauty of it. I was using Pulsar to process 10k events per second(not huge, I know) making calls to the library I mentioned above and populating Clickhouse table. I got experienced with postgres as well. I also became familiar with Github actions, AWS ECS and Redis.The more I do, the more I realize how little I know and that there's so much more to learn. I want to do more of it; write more code, try more approaches, collaborate more and learn from people around me, solve even bigger challenges.

Started learning Go in my free time and was looking for an opportunity to put it to use. I started with writing a tiny package, wrapped around Uber's Zap logger. Then moved on to write test cases for existing microservices, learning how to write our own mocks, breaking down complex piece of logic to make it testable etc. Soon enough, with TDD on my sleeves I was writing APIs, microservices, working closely with other developers, sharing ideas, brainstorming over API/Interface design, better OO design, edge cases, end-user experience. I developed a role based system, state management, a bunch of middlewares, reported an issue in MongoDB, became familiar with Azure, building and deploying pipelines for microservices.All of this increased my appetite for more challenges, on a larger scale. I wanted to go out in the open and fail and wanted my solutions to fail so that I can come up with better plans, better approach and better solutions.

After a brief pause(from a startup that didn't work), I was all pumped up and motivated to solve more challenges. I started here developing a web app in AngularJS before moving on to tackle bigger challenges for a Fortune 500 online payments company. Working my way through Hadoop ecosystem, I developed ETL jobs in HiveQL and shell scripts to automate ETL jobs using UC4 for job scheduling. And all of this led me to another big data project which involved migrating existing solution from SQL Server to Hadoop ecosystem. After this back to back encounter with daunting and weird SQL queries, I moved on to another important project for a Global Energy consultancy group. Spending my initial time building a service that interacts with a legacy spreadsheet solution using .NET Core, I found myself building React components and writing APIs in NodeJS. Soon enough, I got involved in doing code reviews, design discussions and helping others to get up to the speed. Along the way, I picked up a bit of experience with Elasticsearch and AWS DynamoDB. I was looking forward to being a React developer.