You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
What about the issue that message bus based systems would typically hit scaling issues with the message bus being the bottleneck? Were you all aware of problems associated with that approach and take that into your decision process as well?
All distribution methods have scaling challenges. A lot depends on required semantics of the data and update delivery: atomicity, serialization, consistency, freshness, etc. For instance, if you modify 7 entities of different types, will clients observe updates in the same order?
All of the above is true. I was referring more to the difficulty of scaling messaging systems like RabbitMQ. But thanks for the memories. As someone lucky enough to build tools for early cluster systems like PVM it’s amazing to see all the innovations combined into K8s
Ah, yes, I used PVM when at LLNL, and was involved in early discussions around MPI, shortly after the publication of "Attack of the Killer Micros".
It was more the combination of performance and resilience. When modeling entities in realtime and acting as the source of truth for multiple independent controllers, low latency and high freshness are key, esp. in the presence of failures, which produce yet more changes
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
