Over the recent years, software development organizations have seen a major shift in where they build and run their applications. Teams have transitioned from building applications that run exclusively on-prem to microservices applications that are built to run natively in the cloud. This shift gives businesses more flexibility as well as quick and easy access to enterprise services without the need to host costly applications and infrastructure.
TrackJS error monitoring, on your servers. We’re thrilled to announce official support for Node environments and the 1.0.0 release of our Node agent. We’ve actually had Node since sometime last year, but we’re finally formalizing it as a first-class citizen and fully-supported part of TrackJS! Here are some of the cool things you can do with TrackJS for Node.
Infrastructure is a complex and difficult concept for developers. When an issue occurs, where do you even begin to look? I’ve spent years of my life playing the “What looks like one but not like the other” game, wrestling with confirmation bias and hunting through haystacks of logs to find a clue to my hosted applications. This takes away from time spent improving my applications—and it isn’t fun.
Integrating with APIs can be challenging. Each with its own documentation format, SDK patterns, and authentication quirks. Once you get the integration up and running, the harder step is testing and debugging any problems. This part can be exploratory—before you finish building—or as part of problem resolution.
As new advances in software development have allowed developers to increase their velocity and push out new software at ever increasing speeds, one less measured metric is software understandability. Although it probably seems obvious, when building new software the goal should always be to build software that is as simple and easy to understand as possible.
