Only if you cannot change one service without changing the other simultaneously. It's fine to have evolving messages on the queue but they
have to be backwards compatible with any existing subscribers, because you
cannot expect all subscribers to update at the same time. Unless you have a distributed monolith in a monorepo, but at least be honest about it.
Multiple services connecting to the same database has been considered a bad idea for a long time. I don't necessarily agree, but I have no experience in that department. It does mean more of your business logic lives in the database (rules, triggers, etc).
