Building Cloud Networks

Introduction
• IT Automation
• Technology solutions for individual tasks
• Military use of internet before TCP/IP, browsers, network security
• Infrastructure 1.0 (I 1.0)
• Hardware, software & firmware to intelligent software
• Software complexity overtook I (1.0) caused need for virtualization
• Virtualization needed security (Virtualization Security)
• Static Infrastructure & virtualization
Why Collaboration?
• Global Projects, Global scope
• Decentralized teams
• Need for innovation
• Demand for extremely short development cycles.
• Virtual boundary free workspace
Benefits
• Understand business dynamics
• Save cost
• Unlock employee potential
• Customer intimacy
• Your business is no longer constrained by distance or time.
• Achieve a common goal
• Customer loyalty & satisfaction
• Enhance products & services
• Enter new markets
 Service Oriented Architecture (SOA)
• Service Oriented Architecture
• Policies, principles & frameworks that define how network services can
be delivered to increase business outcome.
• Service
• A function that is well defined, self-contained, and does not depend on
the context or state of other services.
• A service is a unit of work done by a service provider to achieve desired
results, have an interface and are message oriented
• SOA Solution
• Set of linked business services that realize an end-to-end business
process, e.g. updating service level agreement of a customer.
What constitutes SOA?
• Improved management control
• Visibility
• Metrics for business processes
• Business process integration
• Composite solutions
• Exposing granular business activities to make them services
• Reuse of existing application assets
SOA vs Cloud
• SOA delivers web services from applications to other programs
• Cloud delivers software services to end users .
• Control & implementation of policies (Governance)
• Cloud services are easy to expand whereas in SOA it is difficult and
expensive because it is based on architecture
• Cloud computing serves as an extension of SOA
 Distributed Component Object Model
• DCOM (Distributed Component Object Model) is a set of Microsoft
concepts and program interfaces in which client program objects
can request services from server program objects on other
computers in a network.
• DCOM is based on the Component Object Model (COM), which
provides a set of interfaces allowing clients and servers to
communicate within the same computer.
• Addition of D is due to DCE/RPC.
• Based on Common Object Requesting Broker Architecture (CORBA).
 Object Request Broker
• An object request broker (ORB) is a middleware which allows
program calls to be made from one computer to another via a
computer network, providing location transparency through
remote procedure calls.
• Based on Common Object Requesting Broker Architecture (CORBA).
Common Object Requesting Broker Architecture
(CORBA)

• Standard to facilitate the communication of systems that are using

diverse operating systems, programming languages and
computing hardware.