Sunday, February 17, 2019

What is Polynimbus Strategy?


IT is the backbone of any organization. To keep the backbone strong, IT managers must make sure whatever the services are being offered to IT users must have high redundancy, high availability and faster time to access it.

A private cloud describes an environment built and operated by a single enterprise for its internal use. These offerings are specifically designed for the different units in the organization with high capex and opex. The biggest disadvantage of the private cloud offering is to maintain the complete life cycle management by the IT team.

IT organizations understood that if they to reduce the cost per bit of the IT infrastructure in that case private cloud would not be the best choice, they must have to opt for public cloud. A public cloud describes a cloud computing offering that can be accessed by the IT users over the internet. It is like you are accessing your google account from anywhere in the world. Examples of public clouds include Microsoft Cloud Services (such as Microsoft Azure or Office 365), Salesforce, Dropbox, and Amazon AWS.

Now the questions comes, when to use public and private cloud. The strategy is up to the IT organizations, they can deploy high load and non-security critical applications over the public cloud and rest all in private cloud.

What is the challenge? Why IT Organizations are not opting for private and public cloud offerings?
Managing both private and public cloud as silos is the biggest challenge. The initial cost of public is too low but when it is being used by most of the IT users in that case metering is the biggest challenge to manage. It’s becoming difficult to keep and eye on the usage of the cloud. Secondly, at same time, the same public offering is being offered by other public cloud providers also. So, does it mean, now we have to shift all the workloads on the other public cloud and till the time migration will complete the new other new cloud provider will reduce it’s cloud offering price. So, what’s the solution of this never-ending story?

“Polynimbus” is the solution of the above-mentioned never-ending story. The term “Polynimbus” refer to a “Multi-Cloud” strategy of adopting multiple cloud providers was first used by John Adams in 2016 while he was working as a Senior Cloud Solutions Architect at Opsgility.

Polynimbus aka muticloud, a cloud computing platform used by single IT organization to manage multiple public and private cloud from single console. The multicloud brings the below mentioned benefits:-
1. Faster Time To Market
2. Single Console to Manage all the public and private cloud offering
3. De-Centralized Architecture in terms of high availability of applications
4. Opt best and breed of the different cloud offerings as per the requirements
5. Get Rid Off Single Cloud Provider

Click Here To Read Rest Of The Post...

Sunday, August 26, 2018

BGP INBOUND TRAFFIC ENGINEERING - Gaining control over your inbound traffic


Inbound Traffic Engineering is an increasingly important problem for the edge networks with multiple upstream ISPs nowadays. To influence the inbound traffic path, such networks can use several methods including:

AS_PATH Prepending
BGP Multi-Exit-Discriminator
The use of BGP Communities with Local Preference
BGP Conditional Route Injection

Download eBook which covers all of the methods (with configuration samples) mentioned above as well as the Automated method of Inbound and Transit Traffic Engineering using Noction Intelligent Routing Platform (IRP).
Click Here To Read Rest Of The Post...

Saturday, August 25, 2018

What is Service Mesh?


Containers are lightweight, efficient and standard way for applications to move between and among the environments.

Micro services is a architectural design for building a distributed application using containers. Micro services are modular in terms of supporting any kind of business requirements. Monolithic code can be divided into smaller parts known as micro services. Micro Services can communicate to each other by using RPC calls.

While implementing Applications require a set of services from their infrastructure like load balancing, traffic managing, routing, health monitoring, security policies and user authentication. These services are often implemented as discrete appliances. Providing an application with these services required going to the appliance to implement and configure the service.

This process was possible when managing dozens of monolithic applications, but as these monoliths become modernized into micro services it isn’t practical to provision hundreds or thousands of containers in the same way. Monitoring, scalability, and high availability can no longer be provided by discrete appliances. These discrete appliances will be from different OEMs and every OEM has different EMS and NMS. It's a big bottle neck for a customer to manage these discrete appliances.

The solution for this problem is call a service mesh — a new way to deliver these services integrated from within the compute cluster itself through APIs that doesn’t require any additional or discrete appliances. This flexible framework removes the operational complexity associated with modern applications.


Click Here To Read Rest Of The Post...