1) Lindex is a leading fashion chain in Europe with 470 stores across 18 markets and annual turnover of €606 million. 2) They implemented an API management strategy using WSO2 API Manager to break up their monolithic systems and enable multiple customer experience teams to develop solutions independently. 3) This allowed for experiments to deliver more customer value and unlock innovation, while standardizing infrastructure and hiding the monolith behind a layer of APIs.

1. Enterprise IT Architect, Lindex
Unlocking Innovation with
API Management
While Breaking Down the Monolith
Johan Edling

2. To empower and inspire women everywhere
Lindex is one of the leading fashion
chains in Europe with 470 stores in
18 markets.
Euro 606 million in turnover 2017
Approx. 5 000 employees.
Head office in central Gothenburg,
Sweden. Founded 1954 in Alingsås,
Sweden
Part of the Finnish listed company
Stockmann since 2007
55% of our garments are made of
sustainable materials

3. Business
● Going from one team to multiple customer experience teams
● Composing applications for a specific user group
● Enabling experiments on what deliver values
Technical
● Hide your monolith behind a layer of APIs
● API is a technique, remember to do proper design.
● Standardization removes infrastructure code
Highlights being covered

4. Online presence after 10 years iterations
Custom WMS
Enova ecommerce system
ERP
Old API CMS
Customer
Synchronization Order item
replenishment
Product
Enrichment
Promotion
Management
Store
solutions
lindex.com
solutions

5. Change agent – Customer loyalty app
Custom WMS
Enova ecommerce system
ERP
Old API CMS
Customer
Synchronization Order item
replenishment
Product
Enrichment
Promotion
Management
Store
solutions
lindex.com
solutions

6. The simple concept
Custom WMS
Enova ecommerce system
ERP
Old API CMS
Customer
Synchronization Order item
replenishment
Product
Enrichment
Promotion
Management
Store solutions
lindex.com
solutions
Customer
app
My Store
apps
Content
Management
Promo Order
WMS
WMS
partner X
Pay
Commerce
API Gateway
lindex.com
solution
other web
solutions
ERP
Customer
Information

7. Enter WSO2 API Manager
Gateway
Gateway
Key
Manager
Key
Manager
Store +
Publisher
Hot standby
Active

8. Active
Mutliple user repositories with WSO2 Identity
Server
API
Manager
Gateway
API
Manager
Gateway
Identity
Server
Identity
Server
API
Manager
Store +
Publisher
Customers
Employees
Active

9. App overview
WSO2 API Manager Gateway Worker WSO2 Identity Server
Lindex
Customer
User Store
Lindex
Customer
Lindex Active
DIrectory
Customer
Bonus
Master
Commerce
Clustered
Sterling
Integrator
Barcode
Customer
Identification
Customer
Master
lindex.com
Customer
Message
AppInfo
Fredhopper
Merchendising
Adobe
Campaign
ERP

10. Extended overview
WSO2 API Manager Gateway Worker WSO2 Identity Server
Lindex
Customer
User Store
Lindex
Customer
Lindex Active
DIrectory
Customer
Bonus
Master
Commerce
Clustered
Sterling
Integrator
Barcode
Customer
Identification
Customer
Master
lindex.com
Customer
Message
AppInfo
Fredhopper
Merchendising
Adobe
Campaign
ERP

11. Innovation happens
WSO2 API Manager Gateway Worker
WSO2 Identity Server
Lindex
Customer
User Store
Lindex
Customer
Lindex Active
DIrectory
Customer
Bonus
Master
Commerce
Clustered
Sterling
Integrator
Barcode
Customer
Identification
Customer
Master
lindex.com
Customer
Message
AppInfo
Fredhopper
Merchendising
Adobe
Campaign
ERP
Franchise
Partners
● Franchise partners ecommerce
● Standalone campaign pages
● POS - Customer lookup
● Czech EET fiscal reporting
● Customer info terminals in store
● My Stock, My Day, My Customer
● GDPR modifications to loyalty
● External Customer Community

12. Customer experience teams
WSO2 API Manager Gateway Worker WSO2 Identity Server
Lindex
Customer
User Store
Lindex
Customer
Lindex Active
DIrectory
Customer
Bonus
Master
Commerce
Clustered
Sterling
Integrator
Barcode
Customer
Identification
Customer
Master
lindex.com
Customer
Message
AppInfo
Fredhopper
Merchendising
Adobe
Campaign
ERP
Franchise
Partners

13. ● Multiple teams developing customer experience solutions
● Customer and commerce engagement in unplanned places
● Experiments are carried out since the development effort is
lower
● Strategy for gradually replacing backend functionality
working
● WSO2 and open-source makes starting out a breeze
The (mid-term) results are in

14. ● Set up statistics of API usage immediately - might seem
expensive but you will regret not having it
● Allocate time for development and changes to API resources
● If necessary use force to setup automatic testing of API
resources
● Make sure API development skills are part of affected teams
● Document guidelines for error handling from both service
implementation and client perspective
Lessons learned - if starting over we would

15. ● API really unlocks possibilities
○ Makes functionality easier to reuse
○ Provides means for teams to be independent
● API is a technique, remember to do proper design.
○ Bounded Context and DDD are very suitable for designing APIs and
resources
● Hide your monolith behind a layer of APIs
○ Plural is important, good starting point for disassembling the monolith
● Centralizing customer identification is key
○ Lets you focus on what is important not infrastructure
○ Find something that can hook into what you have
Highlights

16. THANK YOU
wso2.com