InfoQ Homepage Database Content on InfoQ
-
Reactive Data Access with Spring Data
Christoph Strobl and Mark Paluch discuss non-blocking data access using Spring Data for NoSQl data stores and Project Reactor.
-
Architecting IoT Data Ingestion with Azure Data Services
Mike Benkovich explore the Azure Data Services, explaining the differences between them and showing how to architect an IoT ingestion system in the cloud.
-
Streaming SQL Foundations: Why I ❤Streams+Tables
Tyler Akidau explores the relationship between the Beam Model and stream & table theory, stream processing in SQL with Apache Beam, Calcite, Flink, Kafka KSQL and Apache Spark’s Structured streaming.
-
Polyglot Persistence Powering Microservices
Roopa Tangirala takes a look at Netflix’s common platform used to manage, maintain, and scale persistence infrastructures, sharing the benefits, pitfalls, and lessons learned along the way.
-
Bias in BigData/AI and ML
Leslie Miley discusses how inherent bias in data sets has affected things from the 2016 Presidential race to criminal sentencing in the United States.
-
Handling Billions of Edges in a Graph Database
Michael Hackstein discusses graph databases, the current scalability problems and their solutions.
-
Panel: SQL over Streams, Ask the Experts
The panelists discuss the new generation of Stream Processing engines.
-
Forecasting Using Data
Troy Magennis discusses the top three reasons forecasts fail to match reality, and challenges the assumption that work complexity and effort correlates with delivery time.
-
A Cloud-centric Ecosystem Approach to Ease IoT Development
Yujing Wu discusses two use cases of a cloud-based IoT ecosystem that enables IoT device communication across silos and interoperability across different vendors.
-
Always Available
Claudio Ortolina discusses leveraging Elixir/OTP tools to provide continuous service even when a database is down, walking through the refactoring of an Elixir/Phoenix/PostgreSQL application.
-
Homoiconicity: It Is What It Is
Stuart Sierra demonstrates the power that comes from having the same data representation at all layers: programming language, specification, database, inter-process communication, and user interface.
-
Do We Need Another Key-Value Store?
Hendrik Muhs introduces Keyvi, a key-value store based on 'finite state', describing the concepts, explaining what makes it different and where it is useful.