demo-scene VS python-fake-data-producer-for-apache-kafka

Here’s a great place to dig into things: https://developer.confluent.io

Once you’ve decided on a language to focus on, it’s time to start filling those knowledge gaps. Don’t be discouraged by this step. We all have knowledge gaps, and filling them can be very rewarding. First, you’ll want to make sure you have a good understanding of Kafka basics. Fortunately, there are many resources to help you with this. A web search will turn up many great books and other resources. And, of course, Confluent Developer offers interactive courses ranging from introductory (Apache Kafka 101) to advanced (Kafka Internals), full documentation, and other content to help you get started.

Confluent Developer: Learn Apache Kafka through Confluent Developer tutorials, documentation, courses, blog posts, and examples.

Spend some time on https://developer.confluent.io , especially https://developer.confluent.io/get-started/java/ and look at https://github.com/confluentinc/examples . Those will give really practical examples for how to set up your configs and start consuming

FWIW you'll find a bunch of promo codes over at developer.confluent.io

Kafka streams is a Java library built on the producer/consumer APIs designed to create event-driven microservices on top of Kafka. In general, I recommend exploring https://developer.confluent.io to learn more

For example: https://github.com/confluentinc/demo-scene/tree/master/kafka-connect-zero-to-hero

should I be reading a different material for a first Kafka project and working with a different kind of setup? Now, I can't be unbiased on this one ;) One of the things we're doing with Confluent Developer is to try and create a resource for people to learn Kafka from the ground up, whether they ultimately decide to pursue it on Confluent or not. The fundamentals of Kafka that you'll be learning are going to be as applicable whether you're using Apache Kafka self-managed, or Confluent, or AWS' MSK, or whatever else. Personally I'd this stage I'd use whatever setup you find easiest and least friction to your learning journey. As u/louisvell mentioned, /u/stephanemaarek's courses on Udemy are also very popular, if you wanted a "second opinion" on how to approach learning Kafka.

https://developer.confluent.io they’ve thought about this question very deeply

I had good experience with Aiven in the past, we needed something located in the EU: https://aiven.io/

Access to Aiven

One of the hardest questions we answer for our large enterprise customers is why they should choose Aiven instead of managing their own database and streaming services. It can seem counterintuitive that paying extra for a managed service can save you money. However, when we factor in economies of scale - particularly in regards to access to specialized knowledge and tooling - the case for managed services becomes clear. This was certainly the case for some of our MySQL clients earlier this year, where their investments in Aiven paid off in the form of a quietly managed bug fix.

And Kafka + Kafka Connect has https://www.confluent.io/ https://aiven.io/ https://upstash.com/ (and not quite Kafka, but protocol-compatible, https://redpanda.com/)

Fake data utility - https://github.com/aiven/python-fake-data-producer-for-apache-kafka

For PostgreSQL, similar offerings are: * Google Cloud SQL * AWS RDS * Digital Ocean Postgres * Azure Database for Postgres * Aiven, Instaclustr etc

Aiven - https://aiven.io/

Majority of companies layer DevRel on top of marketing as a sort of afterthought, and that’s usually a recipe for failure. All four co-founders at Aiven (the company where I work at) have been long-time open-source maintainers/contributors and highly value the work of DevRel. Similar examples can be seen at HashiCorp, where co-founder Armon Dadgar has been doing DevRel on the whiteboard since the early days of the company. Technical founders know the value of DevRel and know when to form a DevRel team. This is very different from bringing your first DevRel hire onboard and making them convince the leadership why the company needs DevRel in the first place. If your developer advocate needs to explain to the technical leadership the need for DevRel, that's a red flag for that individual and the company.

I wonder when Aiven https://aiven.io/ (or something similar) will start supporting hetzner.