All sectors

Fashion & Luxury

Long-standing business systems moved to the cloud, domain by domain.

Software for fashion and luxury: modernisation of business systems, work on SAP systems that have existed for years, microservice architectures in the cloud.

For an international luxury fashion brand we moved the processes of a SAP HANA business system to microservices on AWS, starting from the map of its domains. In this sector the core system touches every area of the company: we read it thoroughly before changing it.

Where we step in

  • 01Modernisation of SAP-based business systems
  • 02Domain-driven design and microservices
  • 03Systems communicating over SOAP and WSDL
  • 04Cloud architectures on AWS

What you find when you step in

In luxury, the software that matters is what touches the client in store and what holds orders, stock and CRM together backstage. The two worlds often talk through a long-standing ERP and an enterprise integration bus, with SOAP contracts described by WSDLs and a different vendor for every piece. And when several brands of the same group share a platform, each brand wants its own isolated data and its own rules.

What we have done here

For an international brand we moved the processes of a SAP HANA system into microservices on AWS, first reading the system with the tools of domain-driven design to understand where one domain ended and the next began.

On a clienteling platform shared by four luxury brands, TypeScript and AWS CDK, Aurora PostgreSQL and DynamoDB, seven serverless microservices, we worked on splitting the orders monolith into four separate services: orders, events, queue and queue worker. For a new brand the platform was scaffolded from scratch with the connector to the integration bus and a mocked CRM, so as to move forward while the vendors of the real systems were not yet ready.

How we work in fashion and luxury

The domain map first, then the code. Per-brand isolation treated as an architecture requirement. Integrations with ERP, enterprise bus and CRM built against a contract, with mocks that allow progress in parallel with vendors. Infrastructure described as code, in separate accounts per environment.

Here we bring custom software development and cloud and infrastructure.

What we bring here

Constraints met here

Describe the system. We'll tell you what we see.

Ten minutes, one question at a time. At the end, our honest read of the case. It's the filter, before the call.