主数据管理，正确的方法 [英] Master data management, the right approach

问题描述

我需要制定一个窗口的形式，这是suppossed就一些5-10无关表上执行CRUD操作（比如类别，合作伙伴，位置等）。

I am in need of developing a windows form, which is suppossed to perform CRUD operations on a number of 5-10 unrelated tables (say Categories, Partners, Locations etc).

的无列，数据元素和它们的类型将是为每个表不同。有一个架构宇航员推，使该尽可能地灵活。有人建议，使用户界面是通过保存数据的元信息完全可配置的（是包括SQL查询数据类型引用，UI元素等）在一个配置表，并产生上的从配置飞UI中。

The no of columns, data elements and their types will be different for each table. There is an architecture astronaut push, to make this as flexible as possible. Somebody suggested to make the user interface is completely configurable by saving the meta data information (yeah including SQL queries data type references, UI elements etc) in a configuration table and generating the UI on-the fly from the configuration.

我有一个强烈的感觉，这是会是一个内蒙古平台效应反模式和将最终成为一个维护的噩梦。有人可以请建议是否建立一些在生产系统上建议没有？

I have a strong feeling that this is gonna be a Inner Platform Effect antipattern and will end up as a maintenance nightmare. Can someone please suggest whether building something on a production system is advisable or not?

客户端没有，它必须是配置的任何具体提及。但宇航员推是因为一些新的数据表可能会在不久的将来的可能性。是不是更好地运用KISS / YAGNI原则，在这里，而不是建立一个内部平台？可有人请指教？

The client do not have any specific mention that it needs to be 'configurable'. But the astronaut push is because of the likelihood that a couple of new data tables may come up in the near future. Isn't it better to apply KISS/YAGNI principle here rather than building an inner platform? Can someone please enlighten??

在此先感谢。

推荐答案

对我来说，它听起来就像你对内蒙古平台效应的担忧是有效的。如果我没有理解你的问题，我相信我会建立code来管理你必须使用固态设计的表。然后，当新的表被添加在未来，而以下相同设计图案将是创建一个精心内平台较小的总体工作将它们添加至系统。我的选择肯定是KISS / YAGNI。

To me it sounds like your concerns about the Inner Platform Effect are valid. If I understand your problem correctly, I believe I would build the code to manage the tables that you do have using solid design. Then when new tables are added in the future adding them to the system while following that same design pattern will be less overall work that creating an elaborate Inner Platform. My choice would definitely be KISS/YAGNI.

这篇关于主数据管理，正确的方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！