<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[vyngapp - Medium]]></title>
        <description><![CDATA[A place where vyng founders and employees share about our work. - Medium]]></description>
        <link>https://medium.com/vyngapp?source=rss----4cf8349d9e19---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>vyngapp - Medium</title>
            <link>https://medium.com/vyngapp?source=rss----4cf8349d9e19---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:15:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/vyngapp" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Infra@Vyng — Multi-cloud, Secure, Autoscaled and Cost-effective]]></title>
            <link>https://medium.com/vyngapp/infra-vyng-multi-cloud-secure-autoscaled-and-cost-effective-72b45e2b97c?source=rss----4cf8349d9e19---4</link>
            <guid isPermaLink="false">https://medium.com/p/72b45e2b97c</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[autoscalability]]></category>
            <category><![CDATA[cost-effectiveness]]></category>
            <category><![CDATA[multi-cloud-management]]></category>
            <dc:creator><![CDATA[Rajat Gupta]]></dc:creator>
            <pubDate>Fri, 02 Apr 2021 16:27:51 GMT</pubDate>
            <atom:updated>2021-04-02T16:34:04.815Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Scaling the Server Infrastructure for the Vyng App — Multi-cloud, Security, Autoscaling and Cost-savings for a fast growing Video Caller ID App</strong></h3><p><a href="https://vyng.me/">Vyng</a> began as a fun video ringtone application used by a few thousand people and has exploded in popularity with nearly 20 million downloads across all our apps.</p><p>The app today visualizes phone calls from friends and businesses with video and fullscreen photos. Users on Vyng can choose a video or fullscreen photo as their Caller ID profile to play when they call friends who also have Vyng. Vyng also protects users from spam calls with sophisticated system that identifies both the name of the spam caller and their likelihood to be spam.</p><p>As Vyng grew in usage from 1 million users to 10 million and beyond, we faced a lot of challenges in scaling our application infrastructure to efficiently support our growing user base.</p><p><strong>Autoscaling:</strong></p><p>Our original infrastructure was put together quickly to simply test the app’s validity. But as more and more users joined we had to make bigger investments to solve some of the challenges that come with a fast growing consumer app. These challenges included:</p><ul><li>Manual effort of scaling services up and down</li><li>Wasted resources storing and processing content no longer relevant</li><li>Nondeterministic handling of traffic spikes</li><li>Manual intervention in the system exasperating likelihood of errors</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IGdu-fUHQfbMSSLM" /></figure><p>The first step was to move all our services towards autoscaling. We were able to efficiently migrate all our stateless services in an auto-scaling mode based on CPU and load-based threshold<strong>.</strong></p><p>As a result we got the following benefits:</p><ul><li>No manual efforts in scaling services up and down</li><li>Easy Deployments</li><li>Handled sudden spikes well</li></ul><p><strong>Utilising Power of Multi-cloud:</strong></p><p>We have our infrastructure deployed on AWS and Google Cloud. Both clouds serve our production environment. We utilise the power of both clouds to scale our infrastructure seamlessly for our users in a cost effective manner. We designed our applications in a cloud agnostic way so we can leverage services of different clouds based on our use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/0*gCQhm0loZseAZUuD" /></figure><p><strong>Cost Control:</strong></p><p>Cost control plays a major role in scaling infrastructure. We have taken major steps to lower our overall infrastructure cost and continuously work toward that.</p><ul><li>We do proper profiling to decide resources for our services, so we can avoid resource wastage and serve our users efficiently at the same time.</li><li>Enabling Auto scaling of services helps us to save a major part of cost.</li><li>Spot instances for some of our services and divide them in Multi-cloud to avoid interruption.</li><li>Proper auditing and data purging policies policies for our cloud buckets to avoid unnecessary wastage of storage.</li><li>Created budgets for our Projects and alerts on those for proactively taking action in case of hidden cost.</li><li>Alerts for under-utilised machines.</li></ul><p><strong>Security:</strong></p><p>Our services are distributed in multi-cloud and security is our top most priority. We designed our backend system in such a way that we only have one Global load balancer for receiving all the public traffic over TLS and proper authentication. All our other services are internal only and no other part of infrastructure publicly accessible. We continuously do auditing of our infrastructure and have tools in-place to catch any security loopholes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/0*U-WHR3s_6g8i3uGb" /></figure><ul><li>Google load balancer</li><li>Internal tools behind VPN</li><li>Public traffic over TLS</li><li>All the databases and micro-services are accessed over private IPs and no public access is opened</li></ul><p>The growth at Vyng has been incredible. Scaling up from a Minimal Viable Product used to validate the idea for the app, to supporting tens of millions of users across the world has required our server team to solve complex problems while supporting a vast number of existing users. It’s been a very challenging and rewarding experience and we are excited to continue to work on new solutions as the user base continues to grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72b45e2b97c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyngapp/infra-vyng-multi-cloud-secure-autoscaled-and-cost-effective-72b45e2b97c">Infra@Vyng — Multi-cloud, Secure, Autoscaled and Cost-effective</a> was originally published in <a href="https://medium.com/vyngapp">vyngapp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>