@tobrien what problem are we trying to solve? changes the answer
-
-
Replying to @littleidea
@littleidea well, of course, I was just looking for some nugget like "Don't use RabbitMQ it is made of awful". Low volume stuff... for now.2 replies 0 retweets 0 likes -
Replying to @littleidea
@littleidea@tobrien Disagree. I hate using a database as an integration point between multiple apps. REST or a queue are far better IMHO.1 reply 0 retweets 1 like -
Replying to @markimbriaco
@markimbriaco@tobrien depends on where you are at and where you are going. Low volume, unambitious app, harder to justify added complexity.1 reply 0 retweets 0 likes -
Replying to @littleidea
@littleidea@tobrien Once you have two apps, I think you've crossed the complexity threshold where more structured messaging is needed.1 reply 0 retweets 0 likes -
Replying to @markimbriaco
@markimbriaco@tobrien that's why I asked for context, you can also make more problems than you solve decomposing services prematurely.1 reply 0 retweets 0 likes -
Replying to @littleidea
@littleidea@tobrien That, I agree with. The first question implied >1 services communicating. The database is the wrong place for that.2 replies 0 retweets 0 likes -
Replying to @markimbriaco
@markimbriaco@tobrien Some people when confronted with a problem think "I know, I'll use a message bus." Now they have queue problems.3 replies 0 retweets 0 likes -
Replying to @littleidea
@littleidea@tobrien Clever, but after detangling databases that are shared between N apps more than once, I'd rather have queue problems.2 replies 0 retweets 0 likes
@markimbriaco @littleidea @tobrien strongly agree communicating through databases (even sharing databases between apps) is an antipattern
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.