InfoQ Homepage DevOps Content on InfoQ
-
Serverless Still Requires Infrastructure Management
Serverless architectures employ a wider range of cloud services and make infrastructure stacks more heterogeneous. To effectively manage infrastructure in this era, practices and tools have to evolve.
-
Envoy Service Mesh Case Study: Mitigating Cascading Failure at Lyft
Over the past four years, Lyft has transitioned from a monolithic architecture to hundreds of microservices. As the number of microservices grew, so did the number of outages due to cascading failure or accidental internal denial of service. Today, these failure scenarios are largely a solved problem within the Lyft infrastructure due to the use of the Envoy Proxy as a service mesh.
-
The Cloud Native QA
The advent and widespread adoption of the cloud ecosystem presents a new challenge to the modern-day QA. What does it mean to be QA in a Cloud Native software business?
-
Q&A on the Book "Microservices, a Practical Guide, Principles, Concepts, and Recipes"
The book “Microservices, a Practical Guide, Principles, Concepts and Recipes” by Eberhard Wolff explores technology stacks for microservices-based architectures that can be used on the implementation decisions at the overall system level. Targeted to architects, developers and operations, it provides a set of recipes along with executable samples that can be used to address different needs.
-
Key Takeaway Points and Lessons Learned from QCon New York 2018
This year, at the seventh annual QCon New York, we had in total 143 speakers across the 117 sessions, workshops, AMAs, Open Spaces and mini-workshops. Topics included containers and orchestration, machine learning, ethics, modern user interfaces, microservices, blockchain, empowered teams, modern Java, DevEX, Serverless, chaos and resilience, Go, Rust, Elixir, and security.
-
How Contract Tests Improve the Quality of Your Distributed Systems
Catching bugs at the end of a development cycle is costly, but how do you incrementally test complex distributed systems? In this article, Marcin Grzejszczak looks at an integration testing approach for communication between components. He reviews contract testing, and Spring Cloud Contract, as one solution.
-
Packaging Applications for Docker and Kubernetes: Metaparticle vs Pulumi vs Ballerina
Metaparticle, Ballerina, and Pulumi have introduced different approaches by empowering developers to handle deployment automation within programing language itself without having handwriting YAMLs. This is becoming a trend and will change the DevOps practice in the software industry.
-
Measuring Tech Performance: You’re Probably Doing It Wrong
We try our best to measure our performance, and along the way identify just the right OKRs and KPIs and ABCs. There’s no One True Metric That Matters, but there are some useful guidelines and some all-too-commonly made mistakes. Use measures that focus on outcomes, not output, and measures that optimize for global or team outcomes, not local or individual outcomes.
-
Securing web.config with Encryption Certificates on Windows and Azure
A major area where security is often lax is the web.config file. Usually stored in plain text, an intruder who gains access to this file can then easily access databases and other resources both internal and external. With this technique, secrets in your web.config can be encrypted using the Windows certificate store
-
Building an API Gateway with the Ballerina Programming Language
An API Gateway is a layer in an architecture pattern that allows the business API to focus on the business functionality while taking care of the request dispatching, policy enforcement, protocol translations and analytics. This article is about how we built an API Gateway in Ballerina for the WSO2 API Manager.
-
How to Adopt a New Technology: Advice from Buoyant on Utilising a Service Mesh
When adding a new technology like a service mesh into your production stack, be mindful of the impact this will have on you and your colleagues. Be clear about what problem you are solving, and define appropriate acceptance criteria. Run experiments that attempt to show how a service mesh can make life better for the various stakeholders.
-
Service Mesh: Promise or Peril?
Service meshes such as Istio, Linkerd, and Cilium are gaining increased visibility as companies adopt microservice architectures. The arguments for a service mesh are compelling: full-stack observability, transparent security, systems resilience, and more. But is a service mesh really the right solution for you? This article examines when a service mesh makes sense and when it might not.