Menu is one of the most important elements that defines a restaurant. Most restaurants tend to spend a disproportionate time creating a winning menu. In interactions with our restaurant partners as well, some questions we frequently hear are: &#8220;How do I make my menu more attractive? What changes can I make to my menu to improve orders from customers?” Hence, we have now compiled the best practices to help restaurant partners build an effective menu that appeals to new customers, help get better conversion, and help improve average order values.



A good menu is visually appealing, easy to navigate and communicates the right value. The menu should ideally have high quality dish images, with accurate descriptions, justifiable prices charged by the restaurant partners and be one that is not too long or too repetitive. We recognize that each restaurant is unique and so are its challenges and accordingly this tool has been designed to help each of our restaurant partners with personalized recommendations. Our goal is to empower restaurant partners with the knowledge to make informed decisions that could drive growth. Menu Score helps restaurant partners to convert their menu by drilling down into three key areas:



<ol>
<li>Menu Appeal: Visual Delight and Clarity The first impression is visual: dish photos, descriptions and item classifications. Menu score evaluates the completeness of the menu, analyzing elements such as photos, descriptions, add-ons, and side dishes. Engaging photos and clear descriptions not only captivate customers but also influence their decision-making process. </li>



<li>Menu Browsability: Navigating Success Menu score evaluates the number of items, identifies repeated items, and highlights items not being ordered and guides the restaurant partners in streamlining the menu to enhance customer satisfaction and encourage more orders.</li>



<li>Menu Pricing: Capturing &amp; Creating Value Pricing correctly is an art, and the optimal price charged by the restaurants can often determine a dish’s success. The menu score provides information about how many potential customers dropped off from the outlet after preparing a cart, which provides an insight to restaurant partners to accordingly decide their prices.</li>
</ol>


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" decoding="async" width="640" height="398" src="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=640%2C398&#038;ssl=1" alt="" class="wp-image-13592" style="width:684px;height:auto" srcset="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=1024%2C636&amp;ssl=1 1024w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=300%2C186&amp;ssl=1 300w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=768%2C477&amp;ssl=1 768w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=1536%2C954&amp;ssl=1 1536w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?resize=1568%2C973&amp;ssl=1 1568w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?w=1999&amp;ssl=1 1999w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?w=1280&amp;ssl=1 1280w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/04/image1-3.png?w=1920&amp;ssl=1 1920w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1" /></figure></div>


The Menu Score Advantage



So, what sets Menu Score apart? It&#8217;s not just about analytics; it is about personalized, actionable insights. Here&#8217;s what you can expect:



<ul>
<li>Customized Recommendations: Receive tailored suggestions for improving menu completeness and navigability. </li>



<li>Real-time Updates: Keep the menu dynamic with real-time updates based on changing customer preferences and market trends like Navratri or New Year. Menu Score isn&#8217;t just a tool; it is a restaurant&#8217;s secret mantra for food and delivery ordering success which aims at providing the restaurant partners a higher menu score correlating with a higher menu to cart ratio. It analyzes the menu, pinpoints areas to improve, and unlocks a restaurant&#8217;s true growth potential. </li>
</ul>



So now, say goodbye to guesswork and say hello to Menu Score!&nbsp;



Let&#8217;s embark on this journey together towards culinary excellence and business prosperity.



All our restaurant partners can access their menu score using <a href="https://zom.page.link/r4xK">our merchant dashboard</a>.&nbsp;



Bon Appétit, Team Zomato

Menu Score: How we cracked the Menu Code (and you can too!)

Hackoween: Elevating cybersecurity resilience at Zomato through competitive challenges

The Magnitude of New Year&#8217;s Eve



On this day, every second counts, and every order is a celebration. This year, we didn’t just surpass expectations; we redefined them.



On the technical front, our observability platform adeptly handled 2.2 billion active time series metrics, reaching a peak throughput of 17.8 million per second, showcasing robust performance during peak demand periods. Customers placed about 2 million orders from new restaurants they explored, highlighting adventurous palates and a vast variety of options on Zomato.


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" decoding="async" width="640" height="366" src="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=640%2C366&#038;ssl=1" alt="" class="wp-image-13471" style="width:1276px;height:auto" srcset="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=1024%2C585&amp;ssl=1 1024w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=300%2C171&amp;ssl=1 300w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=768%2C439&amp;ssl=1 768w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=1536%2C878&amp;ssl=1 1536w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?resize=1568%2C896&amp;ssl=1 1568w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?w=1792&amp;ssl=1 1792w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image3-2.jpg?w=1280&amp;ssl=1 1280w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1" /></figure></div>


On the data front, <a href="https://blog.zomato.com/building-a-cost-effective-logging-platform-using-clickhouse-for-petabyte-scale" target="_blank" rel="noreferrer noopener">LogStore</a> &#8211; our in-house logging platform processed 60 TB application logs on that day, with an 80 million RPM peak ingestion rate. Kafka, the backbone of our event-driven architecture, efficiently handled a remarkable rate of 450+ million messages per minute, with the clusters achieving a total peak throughput of 5.6 GBps.



Even with the unprecedented demand of New Year&#8217;s Day, 60% of the orders were successfully delivered within 30 minutes. Our chat support handled a record 19,500 peak concurrent sessions and about 51,400 messages were exchanged per minute, ensuring swift and effective customer service.&nbsp;


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" decoding="async" width="640" height="273" src="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=640%2C273&#038;ssl=1" alt="" class="wp-image-13505" style="width:1283px;height:auto" srcset="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=1024%2C436&amp;ssl=1 1024w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=300%2C128&amp;ssl=1 300w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=768%2C327&amp;ssl=1 768w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=1536%2C654&amp;ssl=1 1536w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=2048%2C872&amp;ssl=1 2048w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?resize=1568%2C667&amp;ssl=1 1568w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?w=1280&amp;ssl=1 1280w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/Frame-1-1.jpg?w=1920&amp;ssl=1 1920w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1" /></figure></div>


Prelude to the Big Night: The Preparation



At Zomato, preparation for NYE is a blend of tech and strategy, setting a benchmark for best practices for ourselves and the industry. We delve deep into each service, ensuring that every aspect is finely tuned for peak performance. Special focus is placed on kill switch reviews, ensuring fail-safes for every scenario. Our preparation includes:



<ul>
<li>Service Design Review: We revisit service design from the ground up, removing excess redundancies to reduce latency and enhance performance.</li>



<li>Database Optimization: Monitoring of database metrics helps identify bottlenecks. Slow queries are optimized, and the database load is reduced by caching frequently used queries.</li>



<li>Incident Analysis: Past incidents are meticulously reviewed for actionable insights, ensuring all loops are closed.</li>



<li>Adherence to Best Practices: Each service is aligned with organizational best practices.</li>



<li>Enhanced Monitoring: Any gaps in monitoring are filled to aid quicker debugging during incidents.</li>



<li>Alerts and Anomalies: Frequent alerts are reviewed, and root cause analyses are conducted. New alerts are added to identify early signs of potential issues.</li>



<li>Kill Switches and Degraded Modes: To prevent lower-tier dependencies from impacting critical services, kill switches are implemented, including modes for degraded operations to maintain core business functions.</li>
</ul>



However, the cornerstone of our preparation is chaos testing and benchmarking.



Chaos-testing: An approach to test a system&#8217;s integrity by simulating and injecting fault into the system. We understand that despite exhaustive reviews, surprises can lurk in the system. Imagine a seemingly minor service causing major disruptions &#8211; this is where chaos testing becomes invaluable. It helps us to uncover hidden dependencies and potential failure points in our complex microservices architecture. We simulate extreme conditions such as:



<ul>
<li>Upstream downtime by injecting unrealistically high response times via our internal service mesh layer built using <a href="https://kuma.io/" target="_blank" rel="noreferrer noopener">Kuma</a></li>



<li>Activation of kill switches to trigger degraded mode, testing system sanity</li>



<li>Cache miss injections to evaluate database reliability under stress</li>
</ul>



Benchmarking: The adage &#8220;At scale, everything breaks&#8221; is not just a cautionary statement, but a fundamental principle that guides our approach to system reliability. As we scale up to meet the massive surge in orders and customer interactions during NYE, hidden vulnerabilities and bottlenecks in our system that are not apparent during regular operations may emerge. These can range from database performance issues, network bottlenecks, to unforeseen failures in microservices that behave differently under heavy load. 



This is particularly crucial when preparing for events like NYE, where the sheer volume of transactions pushes our systems to their limits. Benchmarking provides insights into how they would behave under the extreme pressures of a high-traffic event like NYE.



Benchmarking, especially across our 300+ microservices, presented a unique challenge. Our goal was to push our systems to their limits while ensuring zero negative impact on our operations. To navigate this delicate balance, our SRE team (Site Reliability Engineering) developed an in-house Benchmarking Platform (more on this in a subsequent blog) tailored to these unique challenges. Our approach included:



<ul>
<li>Maintaining data integrity by focusing on read-only traffic or ensuring safe write operations</li>



<li>Isolated benchmarking to prevent simultaneous stress on interrelated systems</li>



<li>Isolation from production workloads. The benchmarking setup is completely independent to prevent any adverse effects on production loads</li>



<li>Gradual increase in load to allow sufficient time for effective autoscaling</li>



<li>Automated and systematic benchmarking to reduce manual effort and ensure timely benchmarking of a large number of microservices</li>



<li>Safe practices such as aborting benchmarking automatically if any critical alerts are triggered or reducing benchmarking load if the error rate on upstream increases</li>
</ul>



The results of this intensive preparation were remarkable. We clocked a total of 14,000 minutes of benchmarking across over 100 services, achieving a peak throughput of 50 million requests per minute, with over 30 billion requests being fired during the benchmarking phase. This extensive exercise, storing around 400 TB of benchmarking requests, provided us with invaluable insights and actionable data, all achieved without a single service outage.



D-Day: Breaking Records, Setting Benchmarks


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" decoding="async" width="640" height="480" src="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=640%2C480&#038;ssl=1" alt="" class="wp-image-13475" style="width:797px;height:auto" srcset="https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=1024%2C768&amp;ssl=1 1024w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=300%2C225&amp;ssl=1 300w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=768%2C576&amp;ssl=1 768w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=1536%2C1153&amp;ssl=1 1536w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?resize=1568%2C1177&amp;ssl=1 1568w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?w=1999&amp;ssl=1 1999w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?w=1280&amp;ssl=1 1280w, https://i0.wp.com/zomatoblog.com/wp-content/uploads/2024/02/image2-1.jpg?w=1920&amp;ssl=1 1920w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1" /></figure></div>


On NYE, Zomato&#8217;s war rooms, spanning multiple businesses, were buzzing with energy as teams from every department came together to monitor services closely. The overall atmosphere was charged, reflecting a day where every aspect comes together in a coordinated, tech-driven effort. The SRE team proactively prescaled the infrastructure to handle the expected surge. We deployed an impressive array of EC2 fleets spanning across 11,000 EC2 instances. This was enough to host our massive armada of ECS services consisting of ~40,000 ECS tasks driving our operations forward. Large screens on every floor in the office displayed performance indicators, keeping the team alert and responsive.&nbsp;



Here is what Raunak Kondiboyina from the Serviceability team had to say about the energy of 31st December at the Zomato office &#8211; “This was my 4th NYE at Zomato. Compared to last year, this year I was feeling pretty relaxed. Most of this confidence was because we started preparing early, and all review processes and benchmarking helped the team gain more confidence.”&nbsp;



Manuj Grover from the Time-service team, shared his emotions for the D-day here &#8211; “It was D-Day, the excitement and anticipation was palpable. It was a mix of nervousness and thrill as we prepared for the highest order volume of the year. The sleepless nights and long hours leading up to the day were fueled by a sense of purpose and determination to ensure everything ran smoothly.”



As NYE descended, energy in Zomato’s war rooms accelerated to match the festive fervor in India. Activity on our app surged as the order rate skyrocketed to 8400 orders per minute. Our systems were operating behind a tsunami of digital traffic at a peak of 80.92 million requests per minute.



We use ElastiCache for our caching needs, on NYE we scaled up our ElastiCache clusters to reach a hefty total of 35 TB in memory across all our microservices. At peak, this fleet saw a significant 20 Gbps of network throughput, managing 1 billion GET operations and around 100 million SET operations per minute, demonstrating the sheer scale of our data handling capabilities.&nbsp;&nbsp;



We rely on a mix of DynamoDB, Aurora RDS and MongoDB as our primary databases. DynamoDB usage peaked with 12.3 million RCUs and 5.2 million WCUs consumed per minute, while our RDS clusters were pushed to their limits handling a scale of 610k select queries and 16,000 write transactions per second. MongoDB clusters aggregated read throughput peaked at 470,000 ops/s scanning 3.3 million docs per second while the write throughput peaked at 180,000 ops/s writing over 1.75 million docs per second.



Storage provisioning was no less formidable, on New Year’s Eve, we provisioned a total of 5.5 petabytes across our infrastructure.



Compared to previous years, we saw a monumental shift in scale and efficiency. While India celebrated New Year’s Eve, our order metrics climbed to unprecedented heights, mirroring the exhilarating atmosphere in our war rooms, and peaked at the moment when we hit the 3 million orders mark, a milestone that not only signified our operational success but also underscored the trust placed in us by millions of customers.&nbsp;



Here’s what Angad Sharma from the Search team had to say about D-Day energy &#8211; “Zomato office during NYE was bubbling with energy, a sweet kind of chaos but a confident &amp; prudent calm like we had everything under control, and no external power can waiver our resolve &amp; pledge for resiliency.”



Post NYE Reflections: Zomato&#8217;s Ongoing Mission of Excellence, Innovation, and Continuous Learning



While our New Year&#8217;s Eve experience has definitely become a springboard for future growth, we also know that we have a lot more to do.



It takes curiosity to learn and unlearn, and as a young Engineering team – with an average age of just 25 years – we already bring the spirit of immense interest and question to work every day. We believe we will hit new milestones this year, and are focused on working towards enhancing Zomato’s ordering and delivery journey at every step of the way. Our goal for 2024? We want to build for the happiest customer experience, and not just a solve to a problem. And in this pursuit, we are bound to make some mistakes, and would have to face many new challenges &#8211; but we will surely get more things right than wrong 🙂



As always, we’re just 1% done.