{"id":306,"date":"2013-03-19T17:52:12","date_gmt":"2013-03-19T14:52:12","guid":{"rendered":"https:\/\/opticstransport.com\/?p=306"},"modified":"2013-03-19T17:52:12","modified_gmt":"2013-03-19T14:52:12","slug":"what-makes-a-cloud-carrier-cloud","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/blog\/what-makes-a-cloud-carrier-cloud\/","title":{"rendered":"What makes a Cloud \u201cCarrier Cloud\u201d?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In cloud, lies&nbsp;opportunities for carriers. What traditional cloud has not been able to achieve, carrier cloud has all those ingredients to &nbsp;deliver. What makes carrier cloud different than traditional public and enterprise clouds?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First few words about what is public and enterprise cloud? Public Cloud are designed&nbsp;on the concept of &nbsp;\u201c Scale Out\u201d i.e. as applications and users grow, more processing power and storage is needed, this necessitates adding more servers to cloud. These are commodity servers, so building and <a href=\"https:\/\/telecomlighthouse.com\/blog\/the-marriage-of-ip-with-otndwdm\/\">expanding network<\/a> in this way is neither expansive nor time consuming. The resilience is always brought in by software and not hardware; in fact hardware is even dubbed as \u201cDesigned-for-failure\u201d. Enterprise cloud, on the other hand, is built&nbsp;on the concept of \u201cScale up\u201d. Processors and Storage capacity in cloud are upgraded&nbsp;rather than \u201cadded\u201d as in public clouds. Since many enterprises are using legacy software which are not designed for the usual \u201cScale Out\u201d concept of public clouds, therefore such enterprises opt for enterprise cloud which is least disrupting and does not need any forklift upgrades. Resilience, here, is based&nbsp;on hardware rather than software.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">Public cloud models have been successful and are here to stay but still work on the \u201cbest effort\u201d model. Other than giving rudimentary SLA ( if any) , they do not provide&nbsp;strict SLA based on guaranteed bandwidth, latency, QoS , downtime penalties and above all guarantees on security of data. Carrier clouds give all these and much more: In addition to strict SLA, <a href=\"https:\/\/telecomlighthouse.com\/blog\/qos-new\/\">high QoS<\/a> and minimum&nbsp;latency they give opportunities for developers to develop applications based on open APIs. For example mobile operators can provide&nbsp;online gaming and multi-play services and develop more applications for their customers based on their carrier clouds. Fixed operators can give VPN services with strict SLA to its customers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Carrier cloud services can open up new opportunities for today\u2019s carriers. With the industry deliberating on going towards \u201cNetwork Virtualization\u201d, carrier cloud can be a stepping stone for this virtualization. Carriers, today are better positioned than public cloud operators to give premium cloud services. They are close to customers. Their POPs are not far away from end users; which ensure&nbsp;minimum latency. They have operation teams in place with established maintenance procedures thus making sure their customers get best support for their services. In short, they can ensure that missing piece of today\u2019s Public clouds: the SLA.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In cloud, lies&nbsp;opportunities for carriers. What traditional cloud has not been able to achieve, carrier cloud has all those ingredients to &nbsp;deliver. What makes carrier cloud different than traditional public and enterprise clouds? First few words about what is public and enterprise cloud? Public Cloud are designed&nbsp;on the concept of &nbsp;\u201c Scale Out\u201d i.e. as [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-306","post","type-post","status-publish","format-standard","hentry","category-sdn"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/306","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/comments?post=306"}],"version-history":[{"count":0,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/306\/revisions"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/media?parent=306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/categories?post=306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/tags?post=306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}