Curated articles, resources, tips and trends from the DevOps World.
Those interested in how data breaches occur should be familiar with the general topography of the Internet. In our previous piece, we discussed the difference between the surface web, deep web and dark web.
The Timeout Design Pattern states that you should not wait for a service response for an indefinite amount of time — you should rather throw an exception instead of waiting for too long. This will ensure that you are not stuck in a limbo state while continuing to consume application resources.
You can’t be in the web development field without hearing about DevOps. It’s like this thing that everybody knows about, but nobody really understands. Hopefully by the time you finish reading this you’ll know what DevOps is and why it exists.
The Internet of Things is coming! It started out as overused marketing hype with no real use case (who needs internet-connected fridges? And who wants the internet-connected toilet paper?).
For most organisations, migrating to the cloud happens in four broad phases. There’s the opportunistic phase: skunkworks projects and new systems start to use public cloud, with or without the blessing of corporate IT. Next there’s the cloud-first stage.
Let me tell you this first. This is not going to be just another post explaining the concepts of Cloud Native Application development. There’s plenty of good material out there describing what is Cloud Native Computing and the problems it’s trying to solve these days.
In this article, we focus our attention on dynamic scaling, aslo known as auto scaling, and why we need applications that can auto scale. This is the fifth article in a series of six articles on terminology used with cloud and microservices. The previous four can be found here:
The Raspberry Pi is an awesome piece of Internet of Things (IoT) hardware and when equipped with the correct modules, it can do powerful things with minimal effort. Take GPS for example.
We all know that when collecting data from different data sources — whether it is an application, server, or service — it is a necessity to have a tracking system that tells what went wrong with your system at a specific time, and to know exactly how your system behaves.
In the SAFE Buzz episode with our Testing and Release Manager Stephen, (05.23) you may recall he spoke briefly about the implementation of Jenkins and the efficiencies it would bring. Currently our build and release processes make use of SaaS products like Travis CI and AppVeyor.
Have valuable insights to share with the DevOps community? Submit your article for publication.
Get the latest DevOps news, tools, and insights delivered to your inbox.
Made with pure grit © 2026 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com