InfoQ Homepage DevOps Content on InfoQ
-
Lessons Learned from Enterprise Usage of GitHub Actions
GitHub Actions is an effective CI tool. However, integrating it into enterprise organizations can be challenging. This article looks at best practices for GitHub Actions in the enterprise.
-
Blue-Green Deployment from the Trenches
Introducing blue-green deployments is often a beneficial improvement. However, with some architectures, it can be challenging to make the changes without impeding deployments. This article covers the challenges and lessons learned in implementing blue-green deployments in the real-world.
-
Securing a Kafka Cluster in Kubernetes Using Strimzi
Deploying an Apache Kafka cluster to Kubernetes is easy if you use Strimzi, but that’s only the first step; you need to secure the communication between Kafka and the consumers and producers, provide RBAC to access topics, spread the secrets correctly to Kafka Connect components and all using a Kubernetes GitOps way.
-
The Importance of Pipeline Quality Gates and How to Implement Them
A quality gate is an enforced measure built into your pipeline that the software needs to meet before it can proceed. This article covers how to get the maximum benefit from quality gates. Making good use of quality gates not only can improve the quality of your software, but it can also improve your delivery speed.
-
An Ode to Unit Tests: in Defense of the Testing Pyramid
The switch to the testing diamond approach has not effectively addressed issues caused by the testing pyramid. Instead, the focus should be on using unit tests correctly within a testable architecture.
-
Java InfoQ Trends Report - December 2022
This report provides a summary of how the InfoQ Java editorial team and several Java Champions currently see the adoption of technology and emerging trends within the Java and JVM space in 2022. We focus on Java the language, as well as related languages like Kotlin and Scala, the Java Virtual Machine (JVM), and Java-based frameworks and utilities.
-
Platform Engineering Needs a Prescriptive Roadmap: a Conversation with Nigel Kersten
Nigel Kersten feels that it is time for a prescriptive roadmap for how to adopt and implement platform engineering. A lack of definition for DevOps enabled early adopters but didn't allow late-majority enterprises to be successful in their adoption of DevOps. The platform engineering community is in danger of repeating this mistake.
-
Colliding Communities, Cloud Native, and Telecommunications Standards
What happens when an ecosystem driven from the bottom up collides with a community characterized by top-down development? The 5g broadband cellular network standard by the 3rd Generation Partnership Project (3GPP), the Network Function Virtualization (NFV) standard by the European Telecommunications Standards Institute (ETSI), and the Service Function Chain RFC (request for comments) are examples.
-
Adopting Low Code/No Code: Six Fitnesses to Look for
When selecting a no-code/low-code platform, six key fitnesses should be examined: purpose fit, cost fit, ops fit, user fit, use-case fit, and organization fit. The IT team should be heavily involved in this decision as they play a pivotal role in helping citizen developers with platform adoption.
-
Using Serverless WebSockets to Enable Real-Time Messaging
This article reviews some of the most common live-user experiences with examples, discusses event-driven architectures to support real-time updates, and introduces common technology choices.
-
API Security: from Defense-in-Depth (DiD) to Zero Trust
Nearly all companies have experienced security incidents but few have an API security policy that includes dedicated API testing and protection. A defense-in-depth approach that includes boundary defense, observability, and authentication is recommended.
-
The Challenge of Cognitive Load in Platform Engineering: a Discussion with Paula Kennedy
In a recent article, Paula Kennedy shared her thoughts on the ever-increasing cognitive load being saddled onto development teams. Although platform engineering is touted as a solution to this challenge, a poorly designed platform will increase the cognitive burden on developers utilizing it. We must also be careful that we are not just transferring that cognitive load onto the platform teams.