对于使用临时表的一般看法是什么？我们经常使用它们从外部供应商导入订单
关于暂存表，我们内部一直存在很多争论。有些人认为临时表已经过时，并且会妨碍构建可重用服务的能力等。据传，这将阻碍业务发展和处理扩展的业务渠道。
我不一定支持或反对这两种选择，但我确实知道，在很多情况下，拥有暂存数据可以挽救生命，并且可以很容易地重新导入我们遇到问题的订单。
只是想看看其他人对暂存数据的看法，以及使用哪些其他方法来处理与我们类似的场景（从外部合作伙伴、亚马逊等处获取订单并将其导入我们的 ERP 系统）。
谢谢，
S
We have been having a lot of internal debate regarding staging tables. Some are view staging tables as archaic and will prevent the ability to build re-usable services, etc. It is also being communicated that these will prohibit the business to grow and handle expanded business channels.
I am not necessarily for or against either option, but I do know that having the staged data has been a life saver in many occasions and has made it really easy to re-import orders we have had issues with.
Just wanted to see what others thought about staging data and what other methods are being used to handle scenarios similar to ours (Taking orders from external partners, Amazon, etc and importing them into our ERP system).
Thanks,
S
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在我工作过的一些地方，我使用了临时表，在其他地方，我使用了其他技术。
每一种都有其自身的优点和缺点。
也就是说，不用担心。
如果出现一些数据馈送需要某种不同于您正在执行的方法的方法，那么您将提出一个新的解决方案。
变化是由需求驱动的。
（就我个人而言，当有人来找我说“我们必须改成X，因为我们现在做的事情效率低下而且糟糕，女巫会来吃掉我们的孩子”时，他们脑海中浮现这样的画面：周二，我们将一个让我们的客户群增加三倍的机会，但前提是我们做这个新事情，但如果我们现在不开始努力，那么我们就会错过这个机会，因为这些潜在客户都不愿意等待，哪怕是一分钟，他们所有人都会要求完全相同的东西，即使我们不知道他们想要什么，我们现在也可以建造他们想要的东西。 快点，快点，不要破坏任何东西，当然，这不是任何事情的运作方式。单个客户（或其他什么）出现并说“嘿，我们需要您的服务，您能接受我们的 XML 吗？”，其响应始终是“当然可以”，然后您就可以完成任务并做出明智的决策，并且计划事情，而不是那些喜欢技术词汇但讨厌了解任何技术的人所喜欢的“斩首鸡”方法）
Some places I've worked I've used staging tables, others I've used other techniques.
Each one has its own advantages and disadvantages.
That said, don't worry about it.
If some data feed comes along that requires some method other than what you are doing, then you'll come up with a new solution.
Change is driven by requirements.
(personally, when someone comes to me and says "We have to change to X because what we do now is inefficient and bad and witches will come and eat our children", they have this image in their minds that on tuesday, we will have an opportunity to triple our client base but only if we do this new thing, but if we don't get cracking on it now, then we'll miss the opportunity because none of those potential clients is willing to wait even a minute and they'll all demand the exact same thing and we can build exactly what they want right now even though we have no idea what they want HURRY HURRY HURRY AND DON'T BREAK ANYTHING. Which, of course, isn't how anything works. A single client (or whatever) comes along and says "Hey, we want your services, can you accept our XML?" to which the response is always "Sure thing", and then you get tasked with it and can make intelligent decisions, and plan things out. As opposed to the "chicken with its head cut-off" methodology preferred by people who like technical words but hate knowing anything tehcnical)
没有理由争论——你有一个有效的系统。任何认为他们的“可重用服务”理论可以做得更好的人都应该放弃或闭嘴。
让他们在您的开发服务器上针对常见的高容量场景构建测试实现，并将其与当前系统进行比较 - 包括故障后恢复和重新导入的标准。
我在工作中也经常听到这样的说法（通常来自刚刚读过一篇有关 SOA 和 XML 的文章的经理），并且在处理大量数据的情况下 - 批量导入到临时表中可以处理比任何类型都要高得多的数据量的网络服务。
There is no reason for a debate - you have a working system. Anyone who thinks their "re-usable services" theory can do it better should put up or shut up.
Let them build a test implementation on your development servers for a common high volume scenario, and compare it to the current system - including criteria for recovery and re-import after a failure.
I hear this all the time where I work as well (usually from managers who just read an article about SOA and XML) and in situations dealing with large amounts of data - bulk imports into staging tables can handle a much higher data volume than any type of web service.