Background

Wagamama’s payment workflow across restaurants, phone / mobile app orders and takeout includes multiple modules developed using multiple programming languages. These modules were outdated and lacked proper documentation, have minimal tests, and having not been adequately maintained. This made them vulnerable to security threats.

It was essential for them to assess these services’ overall infrastructure to decide whether to replace or update them.

Objectives

Given the ask and motivations, the key objectives that enabled Wagamama to make key architectural and technology decisions were:

• A good understanding of the current architecture
• An outline of the services utilising multiple languages and their functionality
• A comparison of a how each service compares to industry standards
• A recommendation on to either keep or replace the services
• A recommendation of the technical architecture and approach (if the services are to be replaced)

Architecture

Evaluation of the existing architecture and enterprise platform solutions. Alongside existing integrations with multiple data sources, third-party providers

Stakeholder Management

Work with stakeholders across the management team and engineering teams to understand existing architecture and recommend the best approach to meeting the requirements

Security & Privacy Governance

Discussion and ideation of new architecture and security governance framework in line with recommendation

Enterprise Integrations

Evaluate the best approach to third-party enterprise technical integrations with multiple providers including Uber Eats, Google, Deliveroo and more