3 ms·

How is this different from REST API? Serious question. Why get downvoted?

• simonh 5y ago
  Because there’s no meaningful way to answer that here. It’s like asking what’s the difference between trawler fishing and open cast mining.
  • temp8964 5y ago
    I don't understand your metaphor. But thanks.
    • simonh 5y ago
      Well, fishing and mining are both resource extraction but apart from that have nothing in common. Kafka and REST both have APIs but apart from that have nothing in common.
• krapht 5y ago
  You're getting downvoted because your question makes no sense. They are not related at all, which means you must not have read the link.
  • temp8964 5y ago
    I read the whole thing. That's why I have the question. So they used to have messages send to everyone (websocks?), now they have the messages persistent in different channels for people to consume. Isn't this just different entry points of a Rest API?
    • krapht 5y ago
      Why are you confusing something that could be used to implement the back-end of a REST API (Kafka) with the idea of a REST API? Your question makes as much sense as: why is <new database X> any different from SQL?
      • temp8964 5y ago
        I got my understanding from the illustrated book... OK. So I didn't get what Kafka is.
• C0d3r 5y ago
  I'm sorry you're getting downvoted, but I think this question is legitimate because the book is peddling Kafka as if it's the only way to do event sourcing. Event sourcing is what you should compare with REST APIs, Kafka is one way of doing it, but you can do the same with any database, as long as you have a way to write things in and read things out and organize them, you can achieve event sourcing. With REST APIs (first few pages of the book), services talk directly with each other, with event sourcing (the rest of the book) services talk with an event store (Kafka in the book) as the intermediary.