当前位置:首页 > 报告详情

传统系统现代化:围绕大型机构建实时系统.pdf

上传人: 竿*** 编号:981541 2025-11-29 80页 4.43MB

1、Legacy ModernizationArchitecting Real-Time Systems With Mainframesjasonjasonroberts.iojasonjasonroberts.ioSonia MathewUnified Web PortalWhere did half the room go?jasonjasonroberts.ioSonia MathewWhat is UWP?A self-service web site for NGs customersBillingPaymentsServiceEnergy UsageFeaturesjasonjason

2、roberts.ioSonia MathewIt wasnt always unified Gas portal Electric portal Multiple mainframesUWP 1.0 was the first attempt to solve this problem and othersjasonjasonroberts.io Sonia MathewCore ProblemUnify presentationUnify dataSolutionUnified Data Model(SQL)ETL:mainframes-SQL-SaaSChallengesETL error

3、 rate led to data quality issuesETL only running a few times per day led to data freshness issuesSingle point of failurejasonjasonroberts.io Sonia MathewEmergent ProblemETL is slow,expensive,and batch orientedSolutionSupplement cache with synchronous R/W to mainframesDrawbacksinelasticcomplex infras

4、tructure under the hoodjasonjasonroberts.io Sonia MathewEmergent ProblemThree systems to keep in sync:MainframeUDM cacheSaaS Web platformSolution An API integration platform was selected to do that synchronizationCritical drawbackSynchronous system doing distributed transactionsjasonjasonroberts.io

5、Sonia MathewExample:Cascading failures due to inelasticityjasonjasonroberts.io Sonia MathewEmergent Problem:SilosNot solved in UWP 1.0jasonjasonroberts.io Sonia MathewOutcomeFailed interactions on the portal drove customers to phone the call center.Customer experience and satisfaction degradedHigh l

6、ead time due to organizational silosjasonjasonroberts.io Sonia MathewEnter UWP 2.0jasonjasonroberts.ioGoals Technical goalsDecouple systemsReduce dependency on external teams and 3rd party solutionsCreate an empowered engineering organizationBusiness goalsReduce call center and software licensing co

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
根据报告的内容,全文主要围绕UWP(Unified Web Portal)的架构和演进展开,以下是关键点: 1. **UWP 1.0**:旨在统一数据模型和展示,使用ETL从主frame到SQL,但面临数据质量、新鲜度和单点故障等问题。 2. **UWP 2.0**:采用领域驱动设计,使用GraphQL和事件驱动架构,解决UWP 1.0的问题,并引入团队拓扑结构。 3. **数据驱动设计**:使用领域驱动设计,将主frame数据作为领域数据,并通过GraphQL提供灵活的数据访问。 4. **团队拓扑**:采用Stream-aligned team、Enablement team和Complicated sub-system team,以支持系统设计和组织结构。 5. **事件驱动架构**:利用CDC(Change Data Capture)和事件流,实现近实时数据同步。 6. **挑战与解决方案**:包括处理事件驱动架构的复杂性、避免单点故障、解决联邦图挑战等。 7. **技术目标**:解耦系统,减少对外部团队和第三方解决方案的依赖,建立强大的工程组织。 8. **业务目标**:降低呼叫中心和软件许可成本,提高客户满意度和平台稳定性。
"UWP 2.0如何提升用户体验?" "主框架数据如何实时同步?" "团队拓扑如何优化系统设计?"
客服
商务合作
小程序
服务号
折叠