Daniel Khan has over 15 years of experience as a full stack developer, architect, and technical lead in the field of web engineering, proving his strong problem-solving skills in hundreds of projects. He is passionate about constant learning, using new technologies, and sharing his findings with others. As a technology strategist, Daniel focuses on driving support for emerging technologies land web performance at Dynatrace.
Four Node.js Gotchas that Operations Teams Should Know about
There is no doubt that Node.js is one of the fastest growing platforms today. It can be found at start-ups and enterprises throughout all industries from high-tech to healthcare.
A lot of people have written about the reasons for its popularity and why it has made sense in “digital transformation” efforts. But when you implement Node.js, do you have to replace your mainframes and legacy software with a shiny new Node.js-based microservice architecture?
Let’s zoom out and walk in the shoes of those who oversee the whole digital value chain: operation and performance teams. What challenges do operation and performance teams face today when they begin to implement Node.js? Does it require an entire gutting of their system?
I’ve been web developer for 17 years and this is what I’ve learned
Sit down at my imaginary campfire to learn how I went from Nerd to pragmatic programmer, how I apply this knowledge today, what I’m still struggling with and how I spot one day hypes and bs.
- Learn to not jump on every hype;
- Explore some principles of pragmatic programming;
- Cover what I’m seeing while working with Enterprises around the globe.