Systems | Development | Analytics | API | Testing

Energy and utilities providers are currently facing more uncertainty than ever before. Volatile prices, geopolitical instability, new technologies and more demands for going green are threatening the future of the entire industry. As a result, their IT teams are under tremendous pressure to start powering digital transformation through productivity improvements, capital efficiencies and development of new revenue streams.

Frequent deployment of APIs can quickly create a software system that is like an overgrown garden, riddled with weeds, bugs, failed integrations, and ill-fitting use cases. Overloaded API collections prevent changes without causing failures. More commonly, they limit the visibility needed to recognize opportunities for feature optimization. Creating a successful API can go a long way to ensuring your organization can avoid many of these problems.

In the past, enterprise software focused on protecting network access through on-premises firewalls and VPNs, working on the assumption that everything within the network was secure. However, today, as accessing data has extended beyond on-premises locations to cloud and hybrid networks, SaaS platforms require a security model that can address a broader range of attack vectors. Zero Trust security addresses this pressing need.

In November of 2014, when NodeSource was still a small consulting group, my teammates Dan Shaw, Rod Vagg, and I were having dinner after a customer engagement, discussing how to bring Node.js production deployments to the same level of polish and tooling capability of the other runtimes our customers were already employing.

In most working environments, there are two things people tend to dislike: First, excessive meetings that prevent employees from making progress on their to-do lists. And second, paperwork. Whether it’s processing financial statements, reading inventory forms, or completing onboarding paperwork for employees, organizations have to deal with a slew of document types to keep operations running.

Strings are arguably the most critical data type in programming, as they make so many things possible. For example, without strings, there would be no emails, text messages, or almost any other computer activity that you can think of because it is the most accessible way of passing information to both technical and non-technical people.

Ensuring accessibility to all types of media is incredibly important, both for enabling as many people as possible to enjoy the media, as well as supporting as many ways as possible for interacting with it. Closed Captioning helps massively with ensuring video content is more accessible by providing a transcription of its audio.

When it comes to procurement in state and local government, agencies’ main complaint is that they can’t buy the goods and services they need fast enough. That’s even at agencies using a digital eProcurement system. While an electronic procurement system should in theory streamline the acquisition of goods and services, many eProcurement systems still abound with stumbling blocks. So what’s slowing down the procurement process, and how can we speed it up?

Versioning REST APIs is crucial for ensuring seamless interactions between software applications. In this tutorial, we’ll discuss how to version REST APIs, ensuring that developers can evolve their APIs without disrupting existing users. Here’s what you need to know about REST API versioning: Table of Contents.