Comment by KptMarchewa
5 years ago
Which complexity? Of running a SQL query on the same database you're already using, vs writing code to support some other new system?
5 years ago
Which complexity? Of running a SQL query on the same database you're already using, vs writing code to support some other new system?
>Of running a SQL query on the same database you're already using
Go back and read OPs link. They create new SQL types, tables, triggers, and functions, with non-trivial and very unforgiving atomic logic. And every system that needs to read or write from this "db queue" needs to leverage specific queries. That's the complexity.
>vs writing code to support some other new system
You mean using a stable well maintained library with a clean and sensible interface to a queueing system? Yes, that is far more simple.
Not necessarily. Many languages like Java already have queuing libraries that operate on rdbms through JPA. So not even a single additional line needs to be written for this to work. We got ours working in a day and it works great. I don't know if other languages have these libraries but I'm inclined to believe they do (at least nodejs has).
Do you have to set up the triggers, tables, and procedures beforehand or how does that work?
3 replies →