• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>International Conference on Fundamentals and Advances in Software Systems Integration >Industry Case Study: Design Antipatterns in Actual Implementations: Understanding and Correcting Common Integration Design Oversights
【24h】

Industry Case Study: Design Antipatterns in Actual Implementations: Understanding and Correcting Common Integration Design Oversights

机译：行业案例研究：设计实际实施中的反坦议：理解和纠正共同的集成设计监督

获取原文
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

The design of any extensible integration solution involving systems intended to communicate efficiently with one another and/or with data repositories usually begins as a proof of concept or prototype, especially if new technologies and platforms are involved. In some instances, the focus on functional features and tight deadlines lead to inadequate attention placed on non-functional system attributes, such as scalability, extensibility, performance, etc. Many design guidelines, best practices, and principles have been established, and antipatterns were identified and explained at length. Yet, it is not uncommon to encounter actual implementations suffering from deficiencies prescribed by these antipatterns. This paper discusses Leaky Abstractions Mixing Concerns, and Vendor Lock-in, as some of the more frequent offenders in case of system integration. Ensuing problems such as the lack of proper structural and behavioral abstractions are described, along with solutions aiming to avoid costly consequences due to integration instability, constrained system evolution, and poor testability. Moreover, unsuitable technology and tooling choices for database design and release management are shown to lead to a systemic incoherence of the data layer models and artifacts, and implicitly to painful database management and deployment strategies.
机译：涉及系统的任何扩展的集成解决方案的设计旨在与彼此和高效通信/或与数据存储库通常开始作为概念或原型的证明，特别是如果新技术和平台参与。在某些情况下，专注于功能性的功能和工期紧张导致注意力放在非功能性的系统属性，如可扩展性，可扩展性，性能等许多设计指南，最佳实践不足，原则已经确立，反模式是确定和长度说明。然而，这种情况并不少见遇到实际实现由这些反规定不足的痛苦。本文讨论漏抽象混合的担忧，以及供应商锁定，因为一些系统集成的情况下，更频繁的罪犯。如缺乏适当的结构和行为的抽象随之而来的问题进行说明，随着解决方案旨在避免因整合不稳定，约束系统的演变，和可测试性较差代价高昂的后果。此外，不当的技术和工具选择的数据库设计和发布管理都表明会导致数据层模型和工件的系统不连贯，并含蓄痛苦的数据库管理和部署策略。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱：kefu@zhangqiaokeyan.com

京公网安备：11010802029741号 ICP备案号：京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有

  • 客服微信

  • 服务号