REST has reigned for a long time in the world of web services. It’s easy to implement, allows standardization through RESTful patterns and has lots of libraries that support and facilitate its development. Then came GraphQL, the famous query language for APIs.

Every day more and more third-party service providers are publishing APIs for their customers to consume, with many of them competing against each other. For instance, with payment APIs, you can use Stripe, Recurly, Chargify, or several others.

In government, mobile devices are both embraced and resisted. The mobility and ease of use afforded by smartphones and tablets helps boost worker productivity even as they open doors for hackers. According to research by Wandera, in 2018 there were 455,121 mobile phishing attacks, 1.9 million Wi-Fi incidents, and 32,846 malware attacks.

In my Puppet travels over the last 10 or so years, one topic has continued to arise time and again, and that has been the ability to scale open source Puppet to thousands of nodes. While the best route is to use Puppet Enterprise for solid support and a team of talented engineers to help you in your configuration management journey, sometimes the right solution for your needs is open source Puppet.

Implementing infrastructure using open-source software significantly reduces the total cost of ownership (TOC) of your infrastructure. Over the last few years, we’ve seen more and more companies moving to open source. These include Netflix, Uber, Visa, eBay, Wikipedia and AT&T. And this trend will only continue to grow. The migration is driven by better economics, improved flexibility, better integration capabilities and thus, the higher business value provided by the open source software.

As we roll into the next decade and IoT becomes commonplace in most organizations, requirements for connectivity will change. Over the last decade of Wi-Fi, we’ve seen a push for faster speeds (high throughput and very high throughput) and recently the ability for greater capacity (high efficiency). Wireless IoT protocols have a different focus. Those requirements are long distance, low power, and flexible architecture. As we consider the next generation, which capabilities rise to the top?

OK, folks. Let’s be real for a moment and acknowledge that everybody, every professional, and definitely every vendor out there is tossing out the phrase “IoT” like flyers on the Las Vegas strip. As an industry, we tend to use IoT to describe a breadth of networked devices, most often headless—those without a user attached—such as cameras, door entry systems, and HVAC controls.

We recently wrote about whether API Gateway can act as a Load Balancer. The answer is yes and, in many cases, they are substitutes for each other. But how should we choose which one to use? In this article, we will dive into more details on how these two types of HTTP networking services compare, using the AWS services as a base level: API Gateway and Application Load Balancer (ALB). Both are highly-scalable services to a point that scalability should not be a concern for most use cases.

Alerting is central to your website, web application, and API monitoring. Getting the right message to the right people is essential to quickly resolving outages and error states. In this article, we walk you through seven aspects you need to consider when setting up the alerting for your monitors. If you need a general overview of how alerting works within Uptrends, we have a Knowledge Base article and an Academy course you may want to visit.