We have a custom workflow engine and process for a lot of our business needs at my company. I wrote it a few years ago, but recently a lot of our existing projects have been migrated over to use the framework. Everyone loves it but our DBAs. Usually I ignore their advice since they still believe that stored procs run faster than parameterized SQL in 2005/2008 databases and consistently have problems keeping transactional logs and such in check.
我们有一个自定义工作流引擎和流程，以满足我们公司的许多业务需求。我几年前写了它，但是最近我们的许多现有项目已经迁移到使用框架。每个人都喜欢它，除了我们的dba。通常我忽略了他们的建议，因为他们仍然相信在2005/2008数据库中存储的procs比参数化的SQL运行得更快，并且始终在控制事务日志等方面存在问题。
Long story short... they do not like that we use a database table for our work queue. It runs fast and we have proper transactional locks and such to keep it running with with multiple instances and threads all querying it at the same time. They are asking we change it to something else... but they have no idea what.
长话短说……他们不喜欢我们为工作队列使用数据库表。它运行得很快，我们有合适的事务锁，这样就可以让它与多个实例和线程同时查询它。他们要求我们把它换成别的东西……但他们不知道是什么。
Are they just being crazy and I should continue to fight to keep our database structure, or am I really crazy for using a database and should be using something else instead for the queue?
他们是疯了，我应该继续努力保持我们的数据库结构，还是我真的疯狂地使用数据库，应该用别的东西代替队列?
1 个解决方案
#1
4
I don't know if I'd say they are just being crazy... but demanding you to change something that is working well without suggesting an alternative seems less than reasonable. I would be curious what a R-DBA would suggest as an alternative to storing workflow data, anyway. Maybe a flat file system? Who knows...
我不知道我是否会说他们疯了……但是，要求你去改变一些有效的东西，而不建议其他选择似乎不太合理。无论如何，我想知道R-DBA对存储工作流数据有什么建议。可能是平面文件系统?谁知道……
There may be merits to changing it. Do they actually have concerns about it as implemented? Is the system causing them problems? I know you suggest that it runs fast and everything is going well, but do they have concerns? Perhaps helping to address those could go a long way toward helping.
改变它可能是有好处的。他们真的对它的实施感到担忧吗?系统给他们带来问题了吗?我知道你认为它运行得很快，一切都进行得很顺利，但他们有顾虑吗?也许帮助解决这些问题对帮助人们大有帮助。
I guess this isn't an inter-office-politics help site at all, but it sounds like there's a larger, over-arching problem between dev/dba at your workplace. It takes someone consistently being the 'bigger person' and starting over with cooperation in mind, no matter how intransigent the other side is, to really fix that sort of thing, if so.
我猜这根本不是一个办公室政治帮助网站，但在您的工作场所，开发人员/dba之间似乎存在一个更大的、全面的问题。它需要一个人始终如一地成为“更大的人”，并从合作的角度出发，不管对方是多么不妥协，如果是这样的话，他真的能解决这类问题。
#1
4
I don't know if I'd say they are just being crazy... but demanding you to change something that is working well without suggesting an alternative seems less than reasonable. I would be curious what a R-DBA would suggest as an alternative to storing workflow data, anyway. Maybe a flat file system? Who knows...
我不知道我是否会说他们疯了……但是，要求你去改变一些有效的东西，而不建议其他选择似乎不太合理。无论如何，我想知道R-DBA对存储工作流数据有什么建议。可能是平面文件系统?谁知道……
There may be merits to changing it. Do they actually have concerns about it as implemented? Is the system causing them problems? I know you suggest that it runs fast and everything is going well, but do they have concerns? Perhaps helping to address those could go a long way toward helping.
改变它可能是有好处的。他们真的对它的实施感到担忧吗?系统给他们带来问题了吗?我知道你认为它运行得很快，一切都进行得很顺利，但他们有顾虑吗?也许帮助解决这些问题对帮助人们大有帮助。
I guess this isn't an inter-office-politics help site at all, but it sounds like there's a larger, over-arching problem between dev/dba at your workplace. It takes someone consistently being the 'bigger person' and starting over with cooperation in mind, no matter how intransigent the other side is, to really fix that sort of thing, if so.
我猜这根本不是一个办公室政治帮助网站，但在您的工作场所，开发人员/dba之间似乎存在一个更大的、全面的问题。它需要一个人始终如一地成为“更大的人”，并从合作的角度出发，不管对方是多么不妥协，如果是这样的话，他真的能解决这类问题。