January 23, 2019 | Episode 17

Using Terraform and Confluent Cloud with Ricardo Ferreira

  • Notes

Tim Berglund hosts Developer Advocate Ricardo Ferreira to discuss the concept of infrastructure as code, as well as the differences between Terraform, Ansible, Puppet and Chef. They also chat about why Terraform is such a big deal, some of the challenges involved with learning it and how Confluent leverages Terraform to achieve multi-cloud support for Confluent Cloud and tools for Confluent Platform.

EPISODE LINKS

Continue Listening

Episode 18February 14, 2019 | 41 min

The Future of Serverless and Streaming with Neil Avery

Neil Avery explores the intersection between FaaS and event streaming applications, the pros and cons of FaaS, important considerations when building streaming applications and five rules that will help you understand how FaaS fits with the event streaming application.

Episode 19February 20, 2019 | 21 min

Ask Confluent #10: Cooperative Rebalances for Kafka Connect ft. Konstantine Karantasis

Gwen Shapira speaks with Konstantine Karantasis, software engineer at Confluent, about the latest improvements to Kafka Connect and how to run the Confluent CLI on Windows.

Episode 20February 25, 2019 | 20 min

Splitting and Routing Events with KSQL ft. Pascal Vantrepote

Tim Berglund chats with Systems Engineer Pascal Vantrepote about the KSQL recipe he created based on a real-life customer use case in the financial services industry. They also discuss the advantages of KSQL, including no Java coding required.

Got questions?

If there's something you want to know about Apache Kafka, Confluent or event streaming, please send us an email with your question and we'll hope to answer it on the next episode of Ask Confluent.

Email Us

Never miss an episode!

Be the first to get updates and new content

We will only share developer content and updates, including notifications when new content is added. We will never send you sales emails. 🙂 By subscribing, you understand we will process your personal information in accordance with our Privacy Statement.