Most IT organizations like to think of themselves as continuously improving. The best ones constantly invest in building new skills, deploying new infrastructure, acquiring new tools, creating new processes, or even tuning what they already have in order to wring more efficiency and productivity out of their environments. Many are migrating to the cloud, as cloud service providers (or CSPs) cheerily advertise three, four or even five 9s of availability (e.g., 99.999% uptime).

Enterprise IT and ISV developers are intrigued by technology benefits of containers and Kubernetes. However, when they go with a recommendation to their senior management to containerize applications, one question is asked – Why do we need to containerize? Didn’t we rehost our application to the cloud?

You can now create monitoring integrations for your technology stack easier than ever before. We’ve recently opened-sourced Sematext’s Monitoring Agent, reworked it, and made it fully pluggable, making it possible for you to collect metrics from a number of additional sources.

In the last few years, the primitive and conservative world is vanishing. In its place is emerging new world whose base is science and technology. The DevOps community has been flourished due to microservices and containerization-based architecture. According to 451 Research, container technology such as Docker and Kubernetes will eventually face the fastest growth in contrast with other cloud-enabling technologies, with an estimated CAGR of 40% through 2020.

Humankind was made to desire success. Everybody wants to be successful. Everybody wants to see successful results of their work. Same at work when you are on a project, same at home when you are trying to make a delicious meal. And the most satisfying feeling afterwards is when you get appreciated, which always is not the case at first couple of trials.

There may be situations when you want to allow time for specific elements to load on your page or ensure certain actions occur within a specific time constraint. In these cases, a Script Time Watcher can be created and applied to individual steps within your script. Script Time Watchers are ideal for the following scenarios: Logon authentication, Credit card/payment method validation, ...

Late October already – where did the year go? Well at least part of it was spent making StackStorm better, and adding new packs and actions to the StackStorm Exchange. Read on for more details about StackStorm 2.9.1, and pack updates to ManageIQ, Jira, ServiceNow, InfluxDB, vSphere, and more.

Where does the time go? The third quarter has flown by, but that doesn’t mean we’ve been resting on our laurels. Maybe it was because we were so busy or having too much fun, but we killed Q3 2017 by 40%! Let’s take a closer look at Q3 2018.

Over the years, automation has become a key component in the management of the entire software release lifecycle. Automation helps teams get code from development into the hands of users faster and more reliably. While this principle is critical to your source code and continuous integration and delivery processes, it is equally essential to the underlying infrastructure you depend on.