![](https://static.wixstatic.com/media/e1158b_dd288b76a22b470d860fa6e770cba437~mv2.jpeg/v1/fill/w_980,h_735,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/e1158b_dd288b76a22b470d860fa6e770cba437~mv2.jpeg)
Gwen Shapira is a co-founder and CPO of Nile. She has 20+ years of experience working with code and customers to build reliable and scalable data architectures - most recently as the head of Cloud Native Kafka engineering org at Confluent.
Gwen is a committer to Apache Kafka, author of “Kafka - the Definitive Guide” and "Hadoop Application Architectures."
You can find her speaking at tech conferences or talking data at the SaaS Developer Community.
Things Databases Don't Do (but should)
Relational databases have been around for 40+ years, so you’d think that by now, they do everything an engineer could possibly need. Surprisingly, this isn’t quite the case. Software architectures, design patterns, devops practices and security all evolved side by side - but not in perfect lockstep. As a result, there are common patterns that developers have to re-implement again and again, while wondering “why can’t my database just do this for me?”. In this talk, we’ll review how software engineering and architectures evolved in the last decade, and how databases can do more to keep up.
Comments