Skip to content

Our client, an Insurance Company, is a leading provider of comprehensive and tailored insurance solutions to consumers and businesses.

Challenge

The client was looking to upgrade their MuleSoft platform and standardize integration design and development. By making these upgrades, the client was hoping to increase efficiency and stability for their operations. They also wanted to improve API delivery and SLAs for related projects and operations. 

Solution

The Orion team was brought on board to lead these initiatives. They upgraded their MuleSoft instance from 4.2 to 4.4. Our team executed the upgrade across 22 production servers and 42 non-production servers including development, model, and color environments. As part of the standardization project, our team followed best practices and moved the version-specific data to global properties to support further scalability. A total of 469 APIs were standardized and 63 were identified as unwanted and removed.  

During the engagement, the team also carried out ESB support activities. From September 2023 through April 2024 the team executed between 36,000 and 39,000 jobs a month, averaging a success rate 99.93%. The team did this while working with the computer room to manually hold jobs during the patching window. 

Impact

See how you can modernize without added risk or complexity.

Schedule a consultation

FAQs

Your questions,
answered.

MuleSoft platform optimization improves how APIs and integrations are designed, managed, and operated. For insurance companies, it helps standardize integration practices, improve platform stability, reduce unused APIs, and support faster delivery of digital services across business systems. 

API standardization helps insurance companies improve consistency, reduce errors, and speed up integration work. It also makes APIs easier to maintain, reuse, and scale across claims, policy, customer service, and operations systems. 

Upgrading MuleSoft improves platform stability, security, and compatibility with newer integration requirements. It also gives organizations more flexibility to support future cloud migration, modern API delivery, and stronger service-level performance. 

Removing unwanted APIs reduces technical debt, lowers maintenance effort, and improves platform visibility. It helps teams focus on active, business-critical integrations instead of spending time managing outdated or unused assets. 

A company should review its integration operating model when API delivery slows down, service levels become inconsistent, or platform maintenance becomes complex. This is especially important before cloud migration, modernization, or large-scale digital transformation. 

MuleSoft supports insurance digital transformation by connecting systems, applications, and data through APIs. This helps insurers improve customer service, automate processes, and enable faster integration across policy, claims, billing, and partner ecosystems. 

ESB support means managing and monitoring enterprise service bus jobs that move data between systems. In large organizations, strong ESB support helps maintain business continuity, reduce failures, and improve the reliability of critical integrations. 

Integration modernization reduces IT costs by removing redundant APIs, improving platform stability, and standardizing development practices. It also lowers manual support effort and helps teams deliver integrations faster with fewer operational issues.

Answer