Netflix’s asgard versus cycligent cloud for web applications

Netflix's asgard versus cycligent cloud for web applications addition to add simplicity


Matthew Irving is really a senior software engineer with more than fifteen years experience of software development, project management software, and deployment strategizing. He presently functions as a Team Manager at Improvement Interactive. 

Remember individuals Microsoft commercials, where average people solve average problems by going “to the cloud”?

I’m guessing some marketing types labored lengthy and difficult to generate that catch phrase, supplying the right mixture of catchiness, intrigue, and confusion.

“What’s the cloud?” millions without doubt requested themselves having seen how their photos could be (gasp!) edited or they might watch (gasp! again) their house TV in the airport terminal. If that’s cloud, I would like in.

The thing is, within the late 2000’s, the tech world was abuzz with “the cloud,” a ubiquitous term that meant something from a Software like a Service (SaaS) product, to some regular website not located in your company’s servers, to apparently an online Desktop link with your desktop computer when the commercials should be believed. And here was Microsoft, prepared to take Home windows users towards the cloud on the magic carpet. Exactly what a strange and beautiful time.

In the last couple of years a lot of us webmaster types have discovered better methods to leverage them. Among the best known and utilized clouds is Amazon . com Web Services (AWS). AWS provides developers also it professionals a method to truly make use of the strengths from the cloud, and it is broadly used by lots of, a lot of companies, from small web application developers to behemoths like Netflix.

Even though AWS is excellent at what it really does, the interfaces could be a bit challenging, and somewhat limited, as you would expect.  On the way, some enterprising institutions have popped up to bridge the space between what AWS provides and just what web-developers need. Today I will compare a few these power tools – Asgard and Cycligent. We’ll compare their weaknesses and strengths which help you choose what’s good for you.

Asgard versus Cycligent Cloud for Web Applications

In their most fundamental level, Asgard and Cycligent Cloud are generally tools employed for web application deployments and cloud management inside the AWS cloud atmosphere. Asgard and Cycligent are tools that actually work along with AWS to complete the gaps within the AWS interface, in addition to add simplicity (or complexity) featuring that do not otherwise appear in AWS.

Produced by Netflix to handle their clearly huge requirement for managing their cloud content, sites, and streaming abilities, the creatively named Asgard (named after the house of the Norse god of thunder and lightning who are able to “control the clouds”) was initially utilized in-house by but for the Netflix teams to handle their very own deployments. Netflix teams work fairly individually, all accountable for their very own deployments, which tool enables these to manage their AWS servers. This Year, Netflix open-sourced Asgard and provided it around the world to make use of.

Similarly, Cycligent Cloud was began through the team of developers at Improvement Interactive, a number one software development firm, with regards to simplifying their cloud development, management and deployments.  Searching for methods to handle multiple synchronised versions of deployments in addition to simplify and “idiot proof” the deployment process, they produced Cycligent Cloud and it is patent pending Holographic Process, and it has opened up up to outdoors users too.

During simple description Asgard and Cycligent Cloud do similar things, they’re really fairly differing products with various focuses and strengths.

Simple versus Complex

Asgard is built to manage the amazingly complex thousands of servers required to provide streaming happy to its 50 million subscribers. Cycligent Cloud is built to simplify and automate the event process, deployment process, and cloud management for many development projects, from small web applications and application servers to enterprise web applications spanning multiple servers.

Whereas Asgard is particularly accustomed to increase the layers of control using their Auto Scaling Groups (ASG) and deployment options (Manage Cluster of Consecutive ASGs, Moving Push), Cycligent Cloud is built to simplify the cloud development while providing you with the control you’ll need and automating the fundamental and customary tasks. A few of these “common tasks” are really complex and quite awesome, like the automated lengthy-worker processing that I’ll discuss afterwards.

An example here may be that Asgard is much like adding more buttons to some cockpit, whereas Cycligent Cloud hides the stuff its not necessary to determine and instantly manages it for you personally.

Deployment Methodologies

One of the greatest reasons for Netflix’s Asgard cloud model includes concepts that AWS doesn’t support directly: Applications and Clusters.

AWS doesn’t presently come with an easy, straightforward methodology that supports clustering or the opportunity to logically affiliate servers into groups according to your internal need. This is where Asgard is available in. This enables segmented teams to handle their very own cluster group deployments inside a more unified manner. This really is aimed at teams with large deployments (along with a monthly Amazon . com Web Services bill rivalling the GDP of countless countries). While this is very helpful and pretty awesome, used, I believe its overkill for several users.

The Cycligent Cloud deployment model differs for the reason that it doesn’t create Groups and Clusters the way in which Asgard does, but breaks out servers for you personally according to their intention. For instance, with Cycligent Cloud’s multiple versioning, it’ll spin up AWS instances for the Production, Sandbox, and Beta sites, either instantly or at the direction. All of the servers are managed with the interface which displays real-time system health monitoring information and enables you to manage them easily. Where Asgard enables you to definitely create relationships between servers as you can see fit, Cycligent Cloud manages its servers according to their role inside your deployment strategy.

Scalability and cargo Management

One awesome feature with Cycligent Cloud is its “long worker” strategy. In enterprise web applications, you will find occasions in which you have lengthy running processes, whether running large reports or performing some complex calculations. Not correctly managed, this may lead to severe bottlenecks and decreased performance. This is where the lengthy workers are available in.

Lengthy personnel are basically server instances, spun as much as handle just these slower demands. You could have your normal instance running, then spin up a lengthy worker instance simply to handle these demands.

But it is not all. Cycligent Cloud instantly monitors your servers for you personally, and when it encounters a recurring bottleneck, it’ll create its very own lengthy worker that you should keep the systems running easily! How’s that for watching the back?

As Asgard is really a more on the job, heavy handed structure, it doesn’t natively inflict process management for you personally. It is not always bad it simply requires more hands on maintenance from you.


Netflix's asgard versus cycligent cloud for web applications as you

One such scenario is managing your different versions – your production site, your sandbox, your everyday builds for testing, in addition to beta previewing for any certain segment of the users. These require different sites and/or instances we all know that. Now you ask , how hard you need to try to manage these versions.

Asgard has two deployment options. The “Manage Cluster of Consecutive ASGs” and also the “Rolling Push.” Regardless of the unwieldy name, the MCSASG version is fairly straight-forward: You spin up a brand new instance, push visitors to it, make certain things are good. When you feel at ease, you decommission the initial instance and you’re all set. If there is a problem you simply push traffic to the initial instance. The Moving Push is much more about pushing one instance at any given time, that is additional time consuming to deploy (and roll in situation of failure).

Neither of Asgard’s deployment methodologies differentiate involving the versions. To create multiple versions of the site for various purposes, you have to manage everything yourself, exactly the same way you typically would.

Managing multiple versions of the source is Cycligent Cloud’s bread and butter. It was included in the woodwork right from the start, and among the best features relating to this service.

Cycligent can create and manage these instances instantly for you personally, without you need to improve your code. All you need to do is pick the atmosphere you need to deploy to and it’ll manage that process for you personally. Push your everyday builds, your beta site, as well as your sandbox simple as cake. And when you’re prepared to push your Beta site to Production, it’s as easy as clicking “Promote.” This selection is actually an amazingly easy process and takes many of the instance management from the equation.


These two systems have lots of effort and brainpower in it to assist in your AWS deployment strategy. Which fits your needs ultimately depends upon what you’re attempting to do.

Cycligent Cloud


  • Multiple versioning done affordably
  • Automated Lengthy worker support
  • Simplified deployments – you don’t need to become an AWS expert
  • Lightweight – designed in Node.js and MongoDB, it’s a effective lightweight system that simple on RAM and CPU


  • Logical grouping of server groups
  • In a position to group and logically manage massive AWS infrastructure
  • Enforces server naming conventions

It truly comes lower to simplicity and simplicity of use versus complexity and much more effective options. If you’re deploying anything approaching the size of Netflix, then Asgard may well be a better fit. Alternatively, if you’re deploying standard sized enterprise web applications spanning multiple instances, then Cycligent Cloud will accelerate and simplify this method for you personally, while still providing you with full control underneath the hood.

Netflix's asgard versus cycligent cloud for web applications problem you

Learn All About the Netflix OSS Cloud


Andrew Finnell: I'm playing LoL while watching this..

Joel Bondurant: Nice talk on AWS.

Delton Childs: Good enough for production but not good enough for GitHub! LMFAO! That's how I feel about everything! :)