Apache Kafka Reviews

DrawSQL Reviews

Apache Kafka mentions (155)

• Building Kafka Producer-Consumer Using Go and Docker

  Kafka is a distributed streaming platform used to build real-time data pipelines and streaming applications. It allows producers to send messages to topics, which are then consumed by various consumers, making it ideal for event-driven architectures. - Source: dev.to / about 2 months ago

• 7 Free Tools for Data Pipeline Reconciliation and Cross-Source Validation

  Apache Kafka is the most widely used distributed event streaming platform and the standard transport layer for event-driven reconciliation architectures. - Source: dev.to / 3 months ago

• How to Build a Dead Letter Queue System for Reliable Data Processing

  For message-queue-based pipelines: RabbitMQ has native DLQ support through dead letter exchanges. Messages that exceed their retry count or their time-to-live are automatically routed to a designated DLQ exchange. Apache Kafka does not have native DLQ semantics, but the standard pattern is to write failed records to a dedicated topic (-dlq by convention) and include the failure metadata in the record headers. - Source: dev.to / 3 months ago

• Idempotency in Data Pipelines: How to Prevent Duplicate Records

  Upsert with timestamp tracking. Keep the upsert approach but track which time windows have been fully processed. On retry, skip windows that are marked complete and reprocess only windows that failed mid-run. The Kafka documentation covers offset management patterns that implement this for stream-based pipelines. - Source: dev.to / 3 months ago

• Real-Time Fraud Detection in Java with Kafka Streams and Vector Similarity

  Apache Kafka allows the payment service to publish a transaction event to a topic, without knowing who will consume it. The fraud service, the notification service, and any other interested component can subscribe to that topic independently:. - Source: dev.to / 3 months ago

DrawSQL mentions (12)

• AI assistance in Development

  With this, I went for designing the db. I went to http://drawsql.app/ and created my first draft. Then exported the DDL and did a bit of back and forth with AI. This is the final draft of the database:. - Source: dev.to / 9 months ago

• How Changing Requirements Shape the Infrastructure of a Software Project

  So I started designing the DB using this cool tool. The project has 2 tables, users and categories . The user can create many categories as he wants so the first approach I took was creating a third table, a union table to store user_id and category_id. With this solution the users are able to create x numbers of categories and we can see assign the category to the user. - Source: dev.to / over 1 year ago

• Creating Diagrams and Databases with Online Tools

  Once you have generated the SQL code, you can convert it into a relational schema (the graphical table model) using DrawSQL. This tool offers:. - Source: dev.to / over 1 year ago

• 🖌️ 5+1 Online Tools for Sketches, Wireframes, Drawings, and Diagrams

  DrawSQL makes it easy for teams to collaborate on creating and maintaining schema diagrams. With a single source of truth, there's no need for manually syncing diagram files between different developers and offline tools anymore. Source: about 3 years ago

• Newbie: Trying to use Supabase Auth fully with its database.

  To be honest, since you are just getting started, I think you should reconsider simplifying this app to begin with. Built something easier and get some more experience before jumping in the ocean. Maybe start by focusing only on the parent company and sub-companies. However, I strongly recommend you to try and make a diagram of your database with relations and columns as it can you a lot of time. I personally use... Source: about 3 years ago