a wild Supposition: can MySQL be Kafka ?
•
0 gostou•1,534 visualizações
Apache Kafka is a distributed publish-subscribe messaging system that uses a distributed commit log to store messages. It allows applications to publish and subscribe to streams of records. The document discusses some similarities and differences between using MySQL and Kafka for messaging, such as Kafka's ability to horizontally scale by adding more brokers with multiple partitions, versus the single partition in a MySQL instance. While unconventional, the document proposes that MySQL could potentially be used as a messaging system like Kafka.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (14)
Semelhante a a wild Supposition: can MySQL be Kafka ?
Semelhante a a wild Supposition: can MySQL be Kafka ? (20)
Mais de vishnu rao
Último
Último (20)
a wild Supposition: can MySQL be Kafka ?
- 1. a Supposi)on: “ can MySQL be Ka5a ? ” vishnu rao – pocketmath.com
- 2. Apache Ka5a
- 3. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log.
- 4. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons:
- 5. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons: – Producer
- 6. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons: – Producer – Topic
- 7. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons: – Producer – Topic – Consumer
- 8. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons: – Producer – Topic – Consumer – Message offset
- 9. Apache Ka5a • A publish-‐subscribe messaging system implemented as distributed commit log. • No)ons: – Producer – Topic – Consumer – Message offset – Broker
- 10. • Producers publish messages to a topic.
- 11. • Producers publish messages to a topic. • Topic is just a par))oned write-‐ahead log. Producers APPEND records to these logs.
- 12. • Producers publish messages to a topic. • Topic is just a par))oned write-‐ahead log. Producers APPEND records to these logs. • Every message is at a OFFSET in the log.
- 13. • Producers publish messages to a topic. • Topic is just a par))oned write-‐ahead log. Producers APPEND records to these logs. • Every message is at a OFFSET in the log. • Consumers consume messages from logs using offset
- 23. What about … • Replicas?
- 24. What about … • Replicas? – MySQL Master – Slave
- 25. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ?
- 26. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write)
- 27. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write) • Mul)ple Par))ons in a ka5a broker Versus
- 28. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write) • Mul)ple Par))ons in a ka5a broker Versus – Single par))on(binlog) in a MySQL instance
- 29. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write) • Mul)ple Par))ons in a ka5a broker Versus – Single par))on(binlog) in a MySQL instance • Data Reten)on ?
- 30. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write) • Mul)ple Par))ons in a ka5a broker Versus – Single par))on(binlog) in a MySQL instance • Data Reten)on ? – How long you keep the binlogs.
- 31. What about … • Replicas? – MySQL Master – Slave • Horizontally Scalable ? – Add more MySQL instances (split write) • Mul)ple Par))ons in a ka5a broker Versus – Single par))on(binlog) in a MySQL instance • Data Reten)on ? – How long you keep the binlogs. • Transac)ons for free versus no txn in ka5a
- 32. This approach might seem unconven)onal & unorthodox.
- 33. This approach might seem unconven)onal & unorthodox. hence It’s a WILD supposi)on “MySQL can be Ka5a.”
- 34. Thank you. We are Hiring! h]p://www.pocketmath.com/jobs.html vishnuhr@pocketmath.com jaihind213@gmail.com sweetweet213@twi]er