Skip to main content
Software Engineering

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.

Required fields*

4
  • 1
    Does this data need to be persisted? You could possibly use some in memory database like memcached or redis. Commented Oct 8, 2015 at 9:40
  • Thank you, well, the only reason why I might need it persisted is for security reasons - just so I know who and when issued a specific command, but that can be saved in a separate database, not linked to this system. So basically yes, this is why I thought about using the MEMORY table type mentioned above, I guess it utilises the same logic as memcached right? Commented Oct 8, 2015 at 10:06
  • Yes, memory should do the same thing. Possibly still worth having a look at different db technologies since the differences can be surprising sometimes. A RDBMS may still introduce some overhead that other technologies can avoid. While 100 users are actually not that much, so it's difficult to say if it's worth the time since there are quite a few technologies that would be interesting here. RethingDB, InfluxDB, VoltDB to name just a few. Commented Oct 8, 2015 at 10:15
  • Aren't you just recreating the logic of a message broker? Why not reuse one of the existing ones (e.g. Kafka)? Commented Oct 8, 2015 at 11:57