Perhaps the most defining trends of the 2020s so far have been abrupt change and mixed signals. IT spending is no different. A mere 3 years ago, COVID-19 swept the globe and thought leaders were calling for the start of a “new normal” and predicted that life on Earth would never be the same – and a major component of that change would be a move to remote-first and digital-everything.

How many software pipelines are required to keep your business running? How many of those build, test, release, or deploy code? The most likely answer here is “I don’t know…” followed by a set of mental gymnastics to try and determine a rough number that is most likely incorrect.

Getting to the root cause of a problem in cloud-native environments requires engineers to navigate through immense complexity within a distributed system. Oftentimes, you didn’t write the code and you lack the background and context to quickly understand what’s going on when a problem occurs. The stakes are even higher when a problem is reported - meaning it’s already started to impact the business and the executives and your customers are not pleased.

Simply defined, multicloud (or multi-cloud) describes a computing environment that relies on multiple SaaS or cloud services for different workloads within a single architecture. In a multicloud approach, organizations may use public cloud providers such as Amazon Web Services (AWS) for infrastructure, Microsoft Azure for platform, and Google Cloud Platform for development.

The Internet of Medical Things (IoMT), a subset of Internet of Things (IoT) technologies, comprises inter-networked devices and applications used in medical and healthcare information technology applications. IoMT devices connect patients, doctors and medical devices — including hospital equipment, diagnostic gear, and wearable technology — by transmitting information over a secure network.

When all your IT systems, your apps and software, and your people are spread out, you need a way to see what’s happening in all these minute and separate interactions. That’s exactly what distributed tracing does. Distributed tracing is a way to tracking requests in applications and how those requests move from users and frontend devices through to backend services and databases.

We’re happy to announce that with the upcoming release of Splunk App for Data Science and Deep Learning (DSDL) 5.1.1 we’re significantly overhauling the build process for containers in DSDL. More and more customers are adopting DSDL for some of their most complex and advanced workloads. In this newest release, we’re making the process of deploying, building and maintaining containers for DSDL more modular, more secure, more robust, and more scalable as well as adding some new features!

Simply put, GitOps applies DevOps practices like version control and CI/CD to infrastructure management. The name GitOps, coined by Weavewerks, is from Git, an open-source version control system that allows teams to manage infrastructure using the same tools and orchestration processes they use for software development.

What are microservices? Microservices are a software approach that creates applications as a loose coupling of specific services or functions, rather than as a single, “monolithic” program. A microservice architecture increases the speed and reliability with which large, complex applications are delivered. What makes a service a microservice? Microservices are defined not by how they’re coded, but by how they fit into a broader system or solution.

Maybe as a kid, you pretended to have a magic wand. You would say something like, “Show me the answer to this long division question” then wave your magic wand and wait for the answer. Sadly, mine never seemed to work – for math questions or to make magical snacks appear. Now, imagine if you had a magic wand for your application stack where you could ask it a question about your data and it would give you immediate insights.