Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This idea of combining concurrent processes and data tables is reminiscent of "tuple spaces" (https://en.wikipedia.org/wiki/Tuple_space, https://software-carpentry.org/blog/2011/03/tuple-spaces-or-...).


To be honest, if your database has decent queuing facilities, it isn’t a bad programming strategy to use the database as a tuple space for piranha processes. You don’t run afoul of corporate architecture teams for using ‘new’ software and you can devolve a lot of business processes into small, independent programs. It also provides an easy way to upgrade parts of your software by freezing a queue table for reads but not writes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: