The role of micro frontends in Cytiva’s XM Cloud journey
Software engineers at leading life sciences company Cytiva share how they transitioned to a composable solution.
5 minute read
Software engineers at leading life sciences company Cytiva share how they transitioned to a composable solution.
5 minute read
Cytiva is a global provider of technologies and services that advance and accelerate the development and manufacture of therapeutics.
The company operates in over 40 countries and territories across Europe, Asia, North and Latin America, and the Middle East.
At a breakout session at Sitecore Symposium 2024, Viktor Kudrenko, Senior Staff Software Engineer at Cytiva and Nikolai Kononov, Staff Software Engineer at Cytiva walked through how they made the move from their monolithic solution to XM Cloud and leveraged micro frontends and microservices architecture.
At Cytiva, the IT department is dedicated to delivering the ecommerce functionality for cytiva.com, with 11 teams located around the world, including Poland, Ukraine, China, Germany, Sweden, and the Netherlands.
Cytiva’s monolithic Sitecore 9.3 solution was handling 170 projects and struggling to meet rising demands. Meanwhile, development teams were facing several frustrating challenges.
As a result, any bug fix or new feature would take five weeks to deliver, which was far from ideal in a competitive market.
Next, Kudrenko and Kononov spoke about their reasons for choosing Sitecore XM Cloud, saying it was a ‘game-changer’ with a MACH architecture that prompted their team to adopt micro frontends and microservices architecture to address their existing challenges.
Several factors influenced Cytiva’s decision to move to Sitecore XM Cloud.
Micro frontends–where independently developed frontends are composed into a greater whole–have been central to Cytiva’s successful move to Sitecore XM Cloud.
Modular: Each micro frontend is a self-contained module that can be developed, tested, and deployed independently.
Composable: Micro frontends are designed to be composed together to create a larger application.
Resilience: As each micro frontend is self-contained, failure in one micro frontend should not affect the overall functionality of the application.
Scalability: It is easier to scale development with a micro frontends architecture as each micro frontend can be developed independently by separate teams.
Maintenance: It is easier to maintain a large application because each micro frontend can be updated and maintained independently.
The session concluded with Kudrenko and Kononov sharing their five most important learnings from their experience leveraging micro frontends.
Learn more about why leading brands are choosing a composable approach.