SOA 世界中的大量数据
我对 SOA 世界还很陌生，而且我已经阅读了很多相关内容。然而，有一件事我仍然不清楚，那就是处理大量数据。
到目前为止，我们公司使用“提要”来集成不同的应用程序。例如，AS400 会吐出大量 xml 文件，这些文件由另一个应用程序处理并存储在其内部数据库中。缺点是我们必须处理此文件源（两端）以及随之而来的所有可能的问题。将其乘以多次，需要集成的不同应用程序、不同的团队、缺乏这方面的总体规则，您可以想象我们今天的处境。
该公司决定采用 SOA 策略，因此我正在研究这个问题。我想知道SOA概念是否包含这样的问题（如上所述的集成问题）。但很难找到有关该主题的信息。是因为 SOA 和大数据量是不可行的，是因为我需要寻找其他地方来解决这个问题（也许是主数据管理），还是我需要开始对抗所有这些大数据量源并禁止它们我们公司？
已经感谢您对此事的任何见解:)
I'm pretty new to the world of SOA and I have read already a lot about it. There's one thing however that is still not clear to me which is handling large data volumes.
So far our company used "feeds" to integrate between different applications. For example, AS400 would spit out a large number of xml files which are picked up by another app that processes it and stores it inside their internal database. The drawback is that we have to handle this file feeds (on both ends) with all possible problems that comes along. Multiply this a number of times, different applications that require integration, different teams, lack on overall rules for this and you can imagine where we are today.
The company decided to adopt a SOA strategy and therefore I'm looking into this matter. I wonder if the SOA concept includes problems like this (integration issues as mentioned above). But it is hard to find information on this topic. Is it because SOA and large volumes is just not doable, is it because I need to look to somewhere else to solve this issue (Master data management perhaps), or do I need to start fighting all this large data volume feeds and ban them from our company?
thanks already for any insight in this matter :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
SOA 只是一组架构原则，这些原则都不会限制或鼓励吞吐量和性能。您可以说 SOA 设计（松散耦合、自治、治理……）和性能设计是两个独立的方面。
许多供应商声称他们拥有“SOA”产品，但实际上您可以在任何平台上构建 SOA，但没有任何产品可以确保您构建正确的 SOA。只需选择最适合您的业务需求的产品或供应商并设置正确的组织结构即可确保您按照 SOA 原则进行构建。
回到您的场景，如果您的数据量非常大（每小时数百万条记录），那么 ETL 产品或自定义软件是最好的。 MDM 更适合数据整合而不是集成。如果您每小时有 10-10 万条记录，则可以使用具有额外优势的集成产品（来自 TIBCO、IBM、Oracle、Software AG、Progress 或开源产品）。
SOA is just a set of architecture principles and none of these principles is restricting or encouraging throughtput and performance. You can say designing for SOA (loose coupling, autonomy, governance, ...) and designing for performance are two independent aspects.
Many vendors claim that they have "SOA" products but in reality you can build SOA on any platform but no product can ensure you are building a proper SOA. Just select the product or vendor that suits best your business requirements and set up the right organizational structure to ensure you are building according to SOA principles.
Back to your scenario, if you've really large volumes (millions of records per hour), ETL products or custom software are the best. MDM is more geared for data consolidation than integration. If you've 10-100 thousands of records per hour, you can use integration products (from TIBCO, IBM, Oracle, Software AG, Progress or open source ones) with added benefits.