1. IMPLEMENTING AN API TIER TO
ENABLE A NEW MOBILE PLATFORM
Thiago Catoto, Magazineluiza

2. Magazine Luiza
700+ STORES
8 FULFILMENT CENTERS
20k+ EMPLOYERS
43 MILLION CONSUMERS
MULTI-CHANNEL STRATEGY

3. The Legacy API
Monolithic
• ~ 150k lines of code
• ~ 1k classes

4. The Legacy API
Slow deployments
• Deploy affects all API paths
• Hard to scale

5. The Legacy API
Hard to make new features
• A lot of mixed responsibility
• Poor code coverage

6. Legacy Architecture
Based on two layers:
• Legacy Core API
• Legacy Mobile API (dedicated)

7. TEAM / API
MOBILE CORE

8. Legacy API

9. Legacy API
MOBILE-API
CORE-API
PUSH

10. Our Challenge
• New API on the way
• Needed a clean transition
• Native app development as mobile
strategy evolution

11. Native App Development
Premises
• Frictionless
• Multichannel
• Personalization

12. Frictionless
• Buy with one touch
• Human Interface Guidelines
• Material Design

13. Multi channel
• Store Lookup
• Store's inventory

14. Personalization
Recommendations
• Abandoned cart
• Last user actions
• Trends

16. Edge

17. Edge

18. Microservices
• Separation of Concerns
• Latency for the win
• Benefits for all involved

19. Blue Print
6 SPRINTS
64 STORIES
208 POINTS
4 TEAM MEMBERS
1 APIGEE DEV CONSULTANT

20. Blue Print
Pros
• Able to make things on the right way
• See the Legacy API as micro services

21. Blue Print
Cons
• Lack of knowledge
• Want to do all with JS

22. Proxies
Stack
• Grunt
• Use policy where you can
• Integration test ( chai )

23. Proxies
• Grouped fully from path
• Format update
• Less request for the client

26. Proxies
oAuth
• Unauthenticated
• Authenticated / Login
• Integrated with Social Login

27. • Easy to use
• Well documented
• Plugins
Grunt

28. Grunt
Tasks
• Validate code style
• Validate swagger
• Deploy on dev, test and prod

29. Test
• Don't mock
• CI with travis
• Black box

30. Test
• Behavior-Driven Development
• Test-Driven Development
• More at 11:40 - 12:20 Wednesday
End to End testing: Bug squashing got api
developers

31. Transition
Migration per group of proxies
• Basket
• Catalog
• Customer

32. Conclusion
• API Management provided the flexibility to
make the architectural transition to
microservices
• When transitioning to microservices think
about decoupling both the mobile and core
APIs

33. Thank you
catoto@luizalabs.com