Let’s face it—distributed streaming is an exciting technology that can be leveraged in many ways. Use cases include messaging, log aggregation, distributed tracing, and event sourcing, among others. Distributed streaming can result in significant benefits for companies that choose to use it, but, when not implemented correctly, it can initiate a frustrating technical debt cycle. How do you know if you’re properly implementing Kafka in your environment?

Congratulations!! After 3 months of hard work, your developer has done an incredible job and your brand new web application is ready to be put online. But wait a minute… Who is going to put it online? Try to ask your developer to do it - there is a good chance that he can’t. Why? Deploying applications is not necessarily a part of their qualifications. And even if he is able to, who's going to make sure it's always available and scale as your business grows?

Don’t let the title mislead you, we love DevOps here at Cycle. Without proper DevOps processes, building and scaling cloud-based applications can become a nightmare for maintainability. A proper DevOps plan brings together an organization’s developers, QA support, and operations teams to pursue the goal of delivering software more predictably. An admirable goal for any team and something that can be immensely helpful for even small teams to become more efficient.

Teams switching from a monolithic application architecture to microservices often face a jarring realization: their time-tested troubleshooting techniques don’t work as effectively. A microservice consists of many independent, distributed, and ephemeral services with varying capabilities for monitoring and logging. Techniques such as stack traces are effective troubleshooting tools in monoliths, but only paint a small portion of the big picture in a microservice-based application.

Chris Goettl is many things to many people. Family man. Homebrewer. PC gamer. Hockey player. And IT security guru and thought leader. As Director of Product Management, Security, at Ivanti, Chris is a highly sought-after expert for his insights into how organizations can strengthen their enterprise IT security in an increasingly demanding environment. Chris hosts a monthly webinar focusing on Patch Tuesday and security vulnerabilities, and frequently blogs about security topics.

Software vulnerabilities are part of our lives in a digitalized world. If anything is certain, it’s that we will continue to see vulnerabilities in software code! Recently the CVE-2020-0601 vulnerability, also known as CurveBall or “Windows CryptoAPI Spoofing Vulnerability”, was discovered, reported by the NSA and made headlines. The NSA even shared a Cybersecurity Advisory on the topic. Anthony previously talked about it from a public sector and Vulnerability Scanner angle.

To complement distributed tracing, runtime metrics, log analytics, synthetic testing, and real user monitoring, we’ve made another addition to the application developer’s toolkit to make troubleshooting performance issues even faster and simpler. Today, we’re excited to introduce Profiling—an always-on, production profiler that enables you to continuously analyze code-level performance across your entire environment, with minimal overhead.

In this age, businesses that provide the best service survive, and when technology becomes the only means to deliver the best service then IT service management is not a question of why but a must. ITSM enables organizations to build a business around better IT support structures, so they can create the best product or service experience. In this blog, we will talk about some of the fundamental questions around ITSM.

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. In the first Five worthy reads of this year, we’ll explore data democratization in detail, from its definition to its pros and cons, and provide some ways to use it for data empowerment.

Source control, aka version control, is the method of tracking and managing changes to software code. Source Control Management (SCM) systems offer a running history of code changes and can be particularly helpful for teams of developers making changes to the same files. As a critical aspect of responsible software development, source control helps developers track code changes, see complete revision history, and revert back to a previous version of a project if needed.