As a network evolves over time, new devices are added, old devices begin to show their age, and some devices are completely forgotten about. It’s a natural consequence of mergers, upgrades, staff turnovers, and other common occurrences that contribute to redundancy or excess complexity in IT infrastructure.

I have good, bad, and good news for you. Let’s start with the first good news: After three months of uncertainty, several countries are starting to reopen their economies and plan their way out of the pandemic. It appears there is finally some light at the end of the tunnel.

With Black Friday and Cyber Monday just behind us, and the Christmas and January sales on the horizon, the cost of downtime is a question that should be of concern to all business owners and e-commerce managers. It should be a concern, but is website downtime always given the consideration it deserves in your business? A company website is a critical component of any modern business, but for businesses who rely on online sales, it really is of paramount importance.

A Content Delivery Network, or CDN, is a collection of proxy servers that are connected to the same origin server, and are geographically distributed relative to end users. Instead of utilizing a single server to respond to user requests, CDN edge servers are able to deliver content more effectively and efficiently to users based on their physical location. For example, if someone from Europe accesses your U.S.-hosted website, it would likely be done through a local U.K.

When was the last time you looked into the loading time of your website on actual end user screens? Do you know that the load time of your website content may significantly vary from different geographical locations? An end user sitting in Los Angeles may face a delay in downloading your web page and content than a user accessing your web page from London. The simple fact is lots of back-end processes are happening behind the scene to deliver your website and content to the end uses.

Website and web application technologies have grown tremendously over the years. Websites are now more than just the storage and retrieval of information to present content to users. They now allow users to interact more with the company in the form of online forms, shopping carts, Content Management Systems (CMS), online courses, etc. The list goes on and on.

One of the central questions we ponder in our work is: what does uptime mean in an interconnected world? You can do everything to ensure 100% reliability, yet still fail. How is this possible in an interconnected world? Shouldn’t there be enough redundancy to ensure nothing breaks if you don’t actively break it? That’s another way of saying technology is great when it works.

Doesn’t it sound magical to predict issues? Detecting a network outage, long before it happens. Yes! It does sound exciting. Now there are numerous network monitoring softwares out there offering this capability. To accomplish this particular goal, businesses around the world have been investing in AI powered network monitoring softwares.

Every application creates logs. Web servers, firewalls, services on your Kubernetes clusters, public cloud services, and more. For companies, being able to collect and analyze these logs is crucial. And the growing popularity of microservices, IoT, cybersecurity, and cloud has brought an explosion of new types of log data. That’s why log management is a huge $2-billion-plus market that’s growing 14% YoY.

In this guide, we’ll cover how you can use Morgan npm to log requests and other aspects of your web application built on Express (or any of the similarly architected frameworks around). So what can Morgan do for you? And when would you need it? As you’ll see in a second if you’re working with Express or a similar framework (such as restify) you’ll have the need to log incoming information about the requests, this framework was designed specifically for that, just keep reading.