Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    #2 is a dreadful solution. You'd be forcing your workers to continuously wade through the entire backlog of trips whether or not anything has changed, and new trips would be put at the back of the line. This could be fully developed in a RDBMS in an hour or two without have to resort to external workers, caches, queue systems or anything else like that. Commented Aug 21, 2019 at 12:30
  • Are you talking about serialization? (In the SQL sense, not in the Java sense). Commented Aug 15, 2020 at 14:16
  • Can you elaborate more on the result: "But result needs to be accurate and realtime.". Does the result need to be another stream? Commented Dec 9, 2021 at 0:38
  • How many records are we talking about like per minute/hour? Commented Aug 1, 2023 at 9:32