28 followers
SWE @Hazelcast. Student @OMSCS. Full-stack TS and JS developer. Aspiring speaker. Blog on an irregular basis. Run BeerJS Voronezh.
Subscribe to my newsletter and never miss my upcoming articles
So, you have decided to move your ass someplace else, seeking a better life. The whole world is at your feet, but "the whole world" is not a specific place where you can be. You have to choose, if not a city, at least a country. Nowadays, there are p...
Large scale equals distributed. Distributed equals inevitable complexity. Complexity at runtime equals extensive monitoring. At Hazelcast, doing distributed systems well is our bread and butter. It means we have no choice but to be huge fans of colle...
Have you heard about "lifting state up"? I guess you have and that's the exact reason why you're here. How could it be possible that one of the 12 main concepts listed in React official documentation might lead to poor performance? Within this articl...
node-config has been serving the Node.js community as pretty much the default config solution for many years. Its simplistic, yet powerful design helped it to spread like a virus across multiple JS libraries. Yet those very design choices don't alway...
How many times did you write logger.info('ServiceName.methodName.') and logger.info('ServiceName.methodName -> done.') for each and every method of your service you wanted to log? Would you like it to be automated and has the same constant signature ...
What's nagging you the most when you think about logging in NodeJS? If you ask me I'm gonna say lack of of industry standards for creating trace IDs. Within this article we'll overview how we can create these trace IDs (meaning we're going to briefly...