Operations | Monitoring | ITSM | DevOps | Cloud

The increasing numbers of business are switching to e-commerce business to sell their products. As of now, there are more than 7,500,000 online stores operating around the world. Naturally, every online retailer is always in the lookout for the best possible ways to outlive their competition. E-commerce businesses cannot compromise on the performance, speed, usability, and scalability of their websites and this is why they need to choose the appropriate technologies diligently.

Learning to build webapps is an exciting process, but it comes with its own set of challenges. As a newer developer, deciding what programming language will bring your big idea to life is a common challenge. There are lots of terrific choices for building webapps on the market. Today, we’ll focus on two of 2019’s most popular options: Node.js vs Python.

As you probably know, source maps allow you to view source code context obtained from stack traces in their original, untransformed form. This view is particularly useful when attempting to debug minified code (like UglifyJS) or transpiled code (like TypeScript or ES6). We’ve made the analogy before, but source maps act as the decoder ring to your secret (minified or transpiled) code.

The MEAN stack has become an increasingly popular choice for developing dynamic applications. Similar to other development stacks like LAMP and Ruby on Rails, MEAN bundles together complementary technologies to provide a ready-made framework for developing and serving applications.

We know Node.js for its lightning-fast performance. Yet, as with any language, you can write Node.js code that performs worse for your users than you’d like. To combat this, we need adequate performance testing. Today, we will cover just that with an in-depth look at how to set up and run a performance test and analyze the results so you can make lightning-fast Node.js applications.

Both Node.js and PHP are popular platforms for websites, APIs, and other types of web content. They have a few similarities, but their differences far outweigh those similarities. In this post, we’ll take a look at how they stack up against each other. It’s Node.js vs. PHP… let’s get ready for the showdown!

2018 was an interesting year for Node.js frameworks and open source software in general. Developer communities discussed the role of corporate sponsorship and how to maintain a project used by millions but not supported financially.

As Winter is coming, we wanted to keep your application warm (up) with these new PM2 Runtime features.

I would like to start by a big THANK YOU, to all PM2 users, contributors, customers, to my team and to the whole Node.js family. Without you, we wouldn't have built such a tool that helps thousands of businesses run their Node.js apps confidently. I deeply love Node.js and I'm still strong on my belief that Node.js is the de facto modern back-end language which increases the productivity of so many businesses, startups, innovators and hackers.

Node.js is an asynchronous JavaScript runtime that is used to develop highly scalable network applications. To help provide more visibility into these dynamic environments, we’re pleased to announce that Datadog APM has officially released support for monitoring Node.js applications, which joins our existing support for Java, Ruby, Python and Go.