Case Study
OEKO-TEX®: Impact Calculator
Summary
Sustainability requires reliable data – especially to achieve the textile industry's ambitious goals by 2030. The Impact Calculator helps companies determine their CO₂ and water footprints. It provides an initial assessment of the materials and processes that contribute most to environmental impact. This innovative tool is available to all production facilities seeking or already holding OEKO-TEX® STeP certification.
Technologies
-
Angular
-
Node.js
-
NestJS
-
prism
-
TypeScript
About the customer
OEKO-TEX® is a registered trademark of the International Association for Research and Testing in the Field of Textile and Leather Ecology. Its globally recognized labels and certificates stand for textile safety and sustainable production conditions at all stages of the supply chain. In addition to product quality, OEKO-TEX® also certifies, in some cases, the ecological and social standards in production facilities.
Challenges
The first project, establishing the right foundation, was crucial, as it would serve as the basis for a broader system migration and integration. The decision to move from the company's traditional JVM-based backend architecture to a pure TypeScript stack represented a bold strategic realignment.
The project exhibited considerable complexity in its business logic, requiring close collaboration with companies specializing in calculating CO₂, water, and energy performance indicators. This necessitated the development team building comprehensive expertise in textile industry processes.
In addition, the project faced a drastic increase in workload, requiring a rapid expansion of the team within a short timeframe. This scaling brought with it the challenges of recruiting, onboarding, and organizing new team members.
Solution
To overcome these challenges, the following measures were implemented:
-
Monorepo architecture: The development team tackled this challenge by designing the project as a monorepo with comprehensive type safety, using OpenAPI and Prisma.
-
TypeScript-only technology stack: By using a unified TypeScript technology stack, frontend developers could essentially work in full-stack roles. This increased the team's flexibility and efficiency. Additionally, seeding scripts and a modular architecture enabled the team to respond quickly to customer feedback.
-
Collaborative development: Throughout the project, the team maintained regular meetings and informal contact with the client, fostering transparency that enabled rapid development. This approach proved highly successful, as the team efficiently delivered the application while simultaneously laying a solid foundation for future applications.
-
Scalability: The architecture and technology decisions our team made facilitated the onboarding of new team members, allowing the team to be expanded efficiently as needed.
Long-term value
The technology stack and architectural patterns that proved successful in this project became a template for subsequent applications, thus demonstrating the long-term value of the original architectural decisions.
