\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={From Service-Oriented Architecture to Cloud Computing},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2018 2018-01-15 (revised: 62 Year 2018 15 January 2018)}
\def\TheID{\makeatother }
\def\TheDate{2018 2018-01-15}
\title{From Service-Oriented Architecture to Cloud Computing}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Ayman G.  Fayoumi}

             \affil[1]{  King Abdulaziz University}

\renewcommand\Authands{ and }

\date{\small \em Received: 10 December 2017 Accepted: 3 January 2018 Published: 15 January 2018}

\maketitle


\begin{abstract}
        


Cloud computing resembles a new paradigm of technology. It suggests deploring technology services without owning the infrastructure behind them. It also releases the burden of maintaining an adequate environment and quality and focusing on the business competency. Service-Oriented Architecture (SOA) is a technology outlook that enables approaching cloud computing. In this paper, we reviewed the main feature of SOA. The main migration from SOA to cloud computing is discussed. Main features and characteristics of cloud computing are presented.

\end{abstract}


\keywords{SOA; cloud computing.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{I. Introduction}]{I. Introduction}\par
n the world where everyone is using computers in day today life, Information Technology plays a crucial role in personal and the business environment. As much as they are used in fulfilling personal needs, they are deployed in the management, operational and the supporting processes in an organization, and hence it became technology centric organization \hyperref[b0]{[1]}. IT suggests dealing with growing issues such as complexity, flexibility, and maintenance. These numerous issues led clients and vendors to adapt skills to handle various responsibilities that support the requirement for their business technologies.\par
Service-Oriented Architecture (SOA) is a paradigm of modernized Information Technology. The design of SOA corresponds suggests shifting towards IT and its applications. As such, SOA is a referenced architecture adopted as a standard architecture \hyperref[b1]{[2]}. In any organization the architecture can be scheme into two ways, one using the scope of the system and the other is using generalization. Figure \hyperref[b0]{[1]} describes the relationship between the architecture types, where SOA represents the reference architecture which guides and constraints to the solution architecture. The way the reference architecture differs from others by its behavior; which is generic. On the other hand, the architecture points to the specific solution to solve the problem. The figure highlights the reference architecture of different scopes like Enterprise architecture, Project Architecture, Software Architecture, etc.  In general, SOA indicates the paradigm of loosely coupled components or services to sustain the requirement for the system development and integration. It is a concept of designing the software and its architecture rather than perceive it as a technology. The basic thought behind this is to express a communication between software agents, which interchanges the messages between service providers and service clients. The clients consistently request the service for its execution from the service provider and in return, this service provider provides the services to the client. Therefore, the clients find the services from agents. Providers are responsible for publishing the services provided to the agents as shown in Figure \hyperref[fig_3]{2 [3]}. This approach towards designing applications using a set of components is considered a seamless contribution of the service coordination. Thus, SOA deployed to obtain services using a strategic framework for the construction of system operation inside and outside the organization \hyperref[b3]{[4]}. Each service in this framework is specific for a distinct task. For example, Figure \hyperref[fig_3]{3} shows the three different people working in a company handle their job in support of one another by giving the services to accomplish their tasks \hyperref[b4]{[5]}. 
\section[{III. Understanding The Services}]{III. Understanding The Services}\par
The service the basic element of SOA. It can resemble a product made by an organization. In order to utilize a service, an interaction between the services provider and consumers are required, clients, suppliers or their partners \hyperref[b20]{[24]}.\par
It is valuable to publish the services with its features so the clients get awareness about the services its cost. This service is characterized into three different features; namely contract, interface, and implementation \hyperref[b0]{[1]}.\par
? Contract: The obligations of both clients and service providers.\par
? Interface: The way of utilizing the service.\par
? Implementation: The actual code running for the services. Given the long practice of using traditional distributed solutions, the implementation of SOA represents a new paradigm for organizations to deliver scalable, reliable and valuable services. It enables seamless communication between clients and providers. Table \hyperref[tab_0]{1} illustrates the comparison between the traditional and SOA. V. Features And Benefits Of SOA SOA plays a vital role in the business. The architecture makes it easy for organizations to meet the on-demand requirements of the current changing market. Some of the features of architecture are summarized as \hyperref[b3]{[4,}\hyperref[b4]{5]}.\par
? Interoperability of services: The communication of services is always carried out through a set of predefined protocols. Communication mechanism can either be synchronous or asynchronous mechanism.\par
? Loosely coupled between the services: In the architecture, the interaction between the service client and service provider are loosely coupled, where the client calls the service without knowing the details on the side of the service provider. ? Message control: Application service layer in SOA allows the management to control the messages for the security purpose. ? Service Abstraction: This constructs the coordination of many services used for the designated process. ? Service Re-usability: The term 'Reuse' support the services through its orientation so it is a employed in the analysis and design process. It also benefits from reusing the components to reduce the redundancy \hyperref[b7]{[8]}. ? Service Transparency: The services are designed to meet the need of the business process. This kind of effect in changing the designing of the business process is known as Agility. ? Service Discoverability: Where every service has to be identified and implicitly used upon needed. All these benefits for the SOA may be positioned into the following areas \hyperref[b7]{[8]}:\par
? Business effectiveness: Where it deals with the agility, awareness of the market, competitive forces, process output and the deployment of the resources as per the business requirement. ? Cost efficiency: Where it deals with the cost reduction for the maintenance, the skills and work needed, improving the performance and the value of the platform\par
? Reduced Risk: There it deals with the quality of services. 
\section[{VI. Implementation Of SOA}]{VI. Implementation Of SOA}\par
Traditionally, tools such as CORBA, DCOM, and RPC were the dominating tools. However, all of these tools have some limitations such as the language specifications, implementation difficulty, etc. SOA suggests an architecture that is the structurally designed for deploying business processes bundled as services throughout its lifecycle. The services are agile according to the requirement changes of the business.\par
As a result, there are three dimensions to consider when implementing SOA; namely, people, process and technology \hyperref[b8]{[9]}. One of the appealing approach to implementing SOA is to deploy ESB, which is a software architecture model that delivers the essential services used for multifaceted architecture. ESB acts as the backbone that uses the technologies for the SOA implementation. Some of the main features of ESB are as follows:\par
? It monitors and controls the routing of messages between the services. ? It resolves the conflict between the communication service components. ? It keeps track of the implementation and versioning of services. ? It enables service such as event control, data modification, and planning, messaging, event queuing, and sorting, etc.\par
Additionally, some of the technologies used to implement SOA \hyperref[b6]{[7]} are\par
? Web Services: The loosely coupled software service, which is delivered over the internet technologies. 
\section[{? Web Service Definition Language (WSDL):}]{? Web Service Definition Language (WSDL):}\par
The mechanism used for describing a web service, which is platform independent.\par
? Simple Object Access Protocol (SOAP): A kind of message formatting between the parties involved in a web service. 
\section[{? Extensible Markup Language (XML):}]{? Extensible Markup Language (XML):}\par
The language used to transport data. Universal Description, Discovery, and Integration (UDDI): This is a registry that assists in registration and organization of the web service description on a searchable directory. 
\section[{VII. SOA And Cloud Collaboration}]{VII. SOA And Cloud Collaboration}\par
Emerging cloud computing technology highlights the creation of services on demand, and hence the communication between SOA and cloud computing becomes profound. As discussed earlier, SOA suggests loosely coupled services to deliver its functionalities. Every time a service is created, users do not require or depend on the knowledge of the way that the service was created. SOA exchanges the data deploying protocols such as SOAP and considering frameworks such as Representational State Transfer (REST). Could Computing, on the other hand, represents an infrastructure on which services can be exchanged and utilized.\par
Thus, implementing SOA on a cloud environment, service consumers can deploy services only upon needed. 
\section[{VIII. What Is Cloud Computing?}]{VIII. What Is Cloud Computing?}\par
Cloud computing resembles connected resources over a network and can be co-located on a public or a private network. It provides a scalable service for application, data, and storage \hyperref[b9]{[11]}. Sometimes the notation is denoted by grid computing, utility computing and on-demand computing \hyperref[b10]{[12]}.\par
Computing resources nowadays represent a key pillar for organizations to deliver their services. In order to function profitably, they have to deploy these computing resources cost-effectively. Cloud computing suggests a feasible approach for sharing resources over the Internet that can be easily accessed and rented for by paying certain fees. Thus users can use services such as word processor, images and video, calendar and so on, over the Internet as shown in Figure \hyperref[fig_4]{5}. The aim goal of this paradigm is to maintain data or service availability and accessibility spanning time and location domains \hyperref[b11]{[13]}.  
\section[{IX. Cloud Computing Technologies}]{IX. Cloud Computing Technologies}\par
There are certain technologies that contribute to cloud computing features such as flexibility, reliability and usability; namely, they are: 
\section[{a) Virtualization}]{a) Virtualization}\par
This technology enables sharing a single application or resources among multiple users. It suggests assigning an indicator to that resource to be called upon required. Figure \hyperref[fig_6]{6}    This paradigm refers to a distributed computing layout where a group of computing facilities from different locations are connected together to accomplish a common task. The grid computing breaks this task into small pieces and those small pieces are connected via the grid as shown in Figure \hyperref[fig_2]{8 [22]}. 
\section[{Figure 8: Grid Computing Architecture d) Utility Computing}]{Figure 8: Grid Computing Architecture d) Utility Computing}\par
This type of computing is a fee model architecture. The users are charged upon their usage of the resources. Technologies like cloud computing, grid computing, and managed IT services are all derivatives of utility computing. 
\section[{X. Cloud Infrastructure Components}]{X. Cloud Infrastructure Components}\par
Cloud infrastructure is a collaborative deployment of several components such as the management server, deployment software, hypervisor, network, storage, and servers. Figure \hyperref[fig_9]{9} shows interrelation of these cloud components  {\ref [22]}.   
\section[{XI. Characteristics Of Cloud Computing}]{XI. Characteristics Of Cloud Computing}\par
The main features of Cloud Computing are summarized as follows \hyperref[b11]{[13]}\hyperref[b12]{[14]}\hyperref[b13]{[15]}: 1. On-demand self-service: The feature allows consumers to access services whenever and wherever they desired to. Service retrieval, deployment, and release. This may take place automatically. 
\section[{Pooling of resources:}]{Pooling of resources:}\par
The resources are pooled together by the service provider to be available for the users. These resources might not be collocated. 3. Elasticity: This makes the nature of provisioning the resources rapid and automated. 4. Scalability: This feature makes the Cloud Computing more appealing as service utilization dictates the scale level at which the resources are offered. 
\section[{XII. Deployment Model}]{XII. Deployment Model}\par
Deployment model is classified according to either the location or type of services provided \hyperref[b14]{[16]}.Based on the resource location, Could Computing is classified as:\par
? Public cloud: Where the services are publicly offered over the Internet. In this model, the service is charged as per the consumer's usage and is introduced and managed by the service provider. This model can also be known as external cloud \hyperref[b12]{[14]}. ? Private cloud: The services in this model are limited to a specific group. The main difference between private and public could is that in the private cloud the data processing is held within the organization premises \hyperref[b11]{[13]}.\par
o The private cloud model can be further classified into two categories: On-premise private cloud: This type of private cloud where the organization uses its own cloud resources located within its own data center. Although this model promises controllable, it may lack some importance cloud features such as scalability and on-demand usage. o Externally hosted private cloud: This model provides some public could feature such as elasticity and scalability, and yet it doesn't allow for resource sharing. \hyperref[b9]{[11]}.\par
? Figure \hyperref[fig_1]{10} illustrates the deployment model \hyperref[b15]{[18]} Figure10: Types of Cloud Computing\par
On the other hand, and based on the services provided, Could Computing is denoted by a suffix "as a Service" as shown in Figure \hyperref[fig_1]{11}. SaaS suggests that the application is provided to the end users on demand. It implies that the installation of the software takes place on the cloud end rather than on the consumer's machine. Therefore, only the services are offered to consumers without any concern on the related infrastructure or perform ability metrics issues. This type of services gets charged per service usage. Figure \hyperref[fig_2]{12} below shows the services being delivered from the service provider to the end consumers. Some of examples of SaaS is the Google Apps, Microsoft suite, Face book \hyperref[b16]{[19]}. 
\section[{Figure12: SaaS framework b) PaaS}]{Figure12: SaaS framework b) PaaS}\par
Platform as a service is another form of service deployment where developers access a platform resource to build the designated applications. These platforms can enterprise to commercial such as .Net or Java environment without installing or downloading the software. Other famous examples of PaaS are Google App Engine, Force.com, and Microsoft Azure \hyperref[b11]{[13]}. 
\section[{c) Infrastructure as a service (IaaS)}]{c) Infrastructure as a service (IaaS)}\par
IaaS is a deployment service model that delivers infrastructure such as computing processing power, data storage, or networking facilities to consumers. This model be referred to as the Hardware as a Service (HaaS). Instead of possessing the hardware, the service providers allow consumers to rent those hardware based on their requirement needs. As shown in Figure \hyperref[fig_12]{13}  \hyperref[b16]{[19]}, some of resources consumers may rent are memory, storage, network, and servers.   
\section[{XIV. Conclusions}]{XIV. Conclusions}\par
In this paper, we presented SOA and Cloud Computing. SOA has some features that enables some of could computing features. Could computing offers an infinite flexible and scalable resources environment while SOA provides adequate connection between the consumers and services. SOA contributes to cloud computing to emerge.\par
Cloud computing suggests paradigm shift from traditional distributed architecture to shared IT environment. It changes the way to deliver the services to the business.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-7.png}
\caption{\label{fig_5}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-8.png}
\caption{\label{fig_6}Figure 6 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{7}\includegraphics[]{image-9.png}
\caption{\label{fig_7}Figure 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{9}\includegraphics[]{image-10.png}
\caption{\label{fig_9}Figure 9 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-11.png}
\caption{\label{fig_10}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-12.png}
\caption{\label{fig_11}Figure11:}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{13}\includegraphics[]{image-13.png}
\caption{\label{fig_12}Figure 13 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{}
\end{longtable} \par
 
\caption{\label{tab_0}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2} \par 
\begin{longtable}{}
\end{longtable} \par
 
\caption{\label{tab_1}2 .}\end{figure}
 			\footnote{© 2018 Global JournalsFrom Service-Oriented Architecture to Cloud Computing} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[ Types of Services in SOA]{b5}\label{b5} 	 		\textit{},  		 \url{http://www.mulesoft.com/resources/esb/services-in-soa}  	 	 		\textit{Types of Services in SOA}  		 	 
\bibitem[Torryarris]{b9}\label{b9} 	 		\textit{Cloud Computing -An overview},  		 			Torryarris 		.  		 \url{http://www.thbs.com/downloads/Cloud-Computing-Overview.pdf}  		 	 
\bibitem[Linthicum (2009)]{b17}\label{b17} 	 		\textit{Cloud Computing and SOA Convergence in Your Enterprise-A Step-by-Step Guide},  		 			David S Linthicum 		.  		September 2009.  	 
\bibitem[Yang and Zhang ()]{b3}\label{b3} 	 		‘Cloud Computing and SOA convergence Research’.  		 			Xiaolong Yang 		,  		 			Huiming Zhang 		.  	 	 		\textit{Fifth International Symposium on Computational Intelligence and Design of IEEE},  				2012.  	 
\bibitem[Srinivas et al. (2012)]{b11}\label{b11} 	 		‘Cloud Computing Basic’.  		 			J Srinivas 		,  		 			K Reddy 		,  		 			Dr A Moizqyser 		.  	 	 		\textit{International Journal of Advanced Research in Computer and Communication Engineering}  		July 2012. 1  (5) .  	 
\bibitem[Dittmann et al. ()]{b18}\label{b18} 	 		‘Cloud Computing Basics’.  		 			Paul F Dittmann 		,  		 			Deepak Rao 		,  		 			Al Choyna 		.  		 \url{http://www.tutorialspoint.com/cloud\textunderscore computing/cloud\textunderscore computing\textunderscore quick\textunderscore guide.htm}  	 	 		\textit{Tutorialspoint, "Cloud Computing -Quick Reference Guide},  				February 2010. 22.  	 	 (Association of Information Technology Professionals) 
\bibitem[Jp (2011)]{b19}\label{b19} 	 		\textit{Cloud Computing Realigns Role of Service Oriented Architecture},  		 			Jp 		.  		July, 2011.  	 
\bibitem[Candrlic (2013)]{b14}\label{b14} 	 		‘Cloud Computing-Types of Cloud’.  		 			Goran Candrlic 		.  		 \url{https://www.gartner.com/it-glossary/community-cloud}  	 	 		\textit{Community Cloud -Gartner IT Glossary}  		March, 2013.  	 	 (published in cloud) 
\bibitem[Velte ()]{b16}\label{b16} 	 		\textit{Cloud Computing: A Practical Approach},  		 			Toby Velte 		.  		2009.  	 
\bibitem[Mahmood ()]{b12}\label{b12} 	 		‘Cloud Computing: Characteristics and Deployment Approaches’.  		 			Zaigham Mahmood 		.  	 	 		\textit{IEEE 11th International Conference on Computer and Information Technology},  				2011. 2011. p. .  	 	 (cit) 
\bibitem[Lian (2012)]{b6}\label{b6} 	 		\textit{Introduction to Service Oriented Architecture},  		 			Ming Lian 		.  		 \url{http://www.cs.colorado.edu/\textasciitilde kena/classes/5828/s12/presentation-materials/lianming.pdf}  		March 2012.  	 
\bibitem[Margolis ()]{b20}\label{b20} 	 		 			Ben Margolis 		.  		\textit{SOA for the Business Developer-Concepts, BPEL and SCA},  				2007. Mc press.  	 
\bibitem[Mell and Grance (2011)]{b13}\label{b13} 	 		 			Peter Mell 		,  		 			Timothy Grance 		.  		 NIST SP-800 -145.  		\textit{The NIST Definition of Cloud Computing},  				September, 2011.  	 
\bibitem[David and Wyld ()]{b10}\label{b10} 	 		\textit{Moving to the Cloud -An Introduction to Cloud Computing in Government},  		 			C David 		,  		 			Wyld 		.  		2009.  	 	 (E-Government series) 
\bibitem[Schmutz et al. ()]{b1}\label{b1} 	 		\textit{Service Oriented Architecture-An Integeration Blueprint},  		 			Guido Schmutz 		,  		 			Peter Welkenbach 		,  		 			Daniel Liebhart 		.  		2010. Packt Publishing. ISBN p. .  	 
\bibitem[Papazoglou ()]{b2}\label{b2} 	 		‘Service-oriented Computing-Concepts, Characteristics and Directions’.  		 			Mike P Papazoglou 		.  	 	 		\textit{Proceeding of the Fourth International Conference on Web Information Systems Engineering of IEEE},  				 (eeding of the Fourth International Conference on Web Information Systems Engineering of IEEE)  		2003.  	 
\bibitem[Lonnekedikmans and Van Luttikhuizen ()]{b0}\label{b0} 	 		\textit{SOA made Simple},  		 			Ronald Lonnekedikmans 		,  		 			Van Luttikhuizen 		.  		2012. Packt Publishing.  	 
\bibitem[Erl ()]{b4}\label{b4} 	 		\textit{SOA-Principles of Service Design},  		 			Thomas Erl 		.  		2007. Prentice Hall.  	 
\bibitem[Liu (2009)]{b8}\label{b8} 	 		\textit{SOA-Service Oriented Architecture},  		 			Mike Liu 		.  		 \url{http://www.packtpub.com/article/soa-service-oriented-architecture}  		July 2009.  	 
\bibitem[Webmethods ()]{b7}\label{b7} 	 		\textit{The Business case for SOA},  		 			Webmethods 		.  		2005.  	 
\bibitem[Ames (2012)]{b15}\label{b15} 	 		\textit{Types of Cloud Computing},  		 			Josh Ames 		.  		 \url{http://blog.appcore.com/blog/bid/167543/Types-of}  		December, 2012.  		 			Cloud-Computing-Private-Public-and-Hybrid-Clouds 		 	 
\end{bibitemlist}
 			 		 	 
\end{document}
