Will real-time data processing replace batch processing?
At Confluent's user conference, Kafka co-creator Jay Kreps argued that stream processing would eventually supplant traditional methods of batch processing altogether.
Absolutely: Businesses operate in real-time and are looking to move their IT systems to real-time capabilities.
Eventually: Enterprises will adopt technology slowly, so batch processing will be around for several more years.
No way: Stream processing is a niche, and there will always be cases where batch processing is the only option.
STORIES BY Jennifer Riggins — PAGE 3
Can Masking Metadata Boost Open Source Security, Diversity?
Engineering Management During Wartime
Job Sharing Can Help Retain Tech Workers. But It’s Not Easy.
Is Tech’s 4-Day Work Week Coming? Not Yet, but Stay Tuned.
The Future of Flexible Work in the Tech Industry
Pulumi Pursues Polyglotism to Extend Infrastructure-as-Code
Kelsey Hightower on How to Become a Better Engineering Team
The Future of Open Source Contributions from KubeCon Europe
The Need to Decouple Human Error from Incident Response
FinOps: How Kubernetes Teams Can Best Work with Finance
James Webb Space Telescope and 344 Single Points of Failure
Vanguard’s Iterative Enterprise SRE Transformation
Can SRE Bring Governance and Compliance into the Future?
Critics of ‘Deceptive Design’ Push for a More Ethical UX
Charity Majors’ Recipe for High-Performing Teams
Is Storage-as-Code the Next Step in DevOps?
How to Build a Roadmap to App Modernization
How to Build a Zero Trust Culture
The Work-War Balance of Open Source Developers in Ukraine
3 Hiring Lessons Learned from 2,600 Engineering Candidates
How to Support Teammates Living in Ukraine — or Any War Zone
How Amazon Prime Video Engineering Builds Team Resilience
A Guide to OKRs and Overcoming the Pain of Them
The State of Sustainable Architecture Practices in 2022
How to Hire (and Keep) Software Devs for Complex Systems
How Government Open APIs Can Address Structural Inequity
App Modernization: Why ‘Lift and Shift’ Isn’t Good Enough
Bring a More Inclusive Developer Strategy to APIs