3 Cloud Services
3 Cloud Services
3 Cloud Services
Cloud Services
Reference
Contents for this PPT is taken from the following
books
1. Buyya R., Vecchiola C., & Selvi S. T. (2013).
Mastering cloud computing: foundations and
applications programming,
2. Cloud Computing Black Book by Kailash
Jayaswal, Jagannath Kallakurchi, Donald J.
Houde and Dr. Deven Shah. Dreamtech
Publications
3. “Cloud computing bible” by Sosinsky, Barrie.
John Wiley & Sons, 2010.
2
SPI Model
Cloud Computing System
Infrastructure as a Service
Multi-Tenancy Intended for Single or small group of Supports Hundreds of users, each with
users multiple active projects
User End Application based tools, browsers Web browser based tools.
Points
Deployment Deployment and scalability are left for Scalability, failover, and load balancing
installation and go live phases are the basic building blocks
Runtime Development solutions are usually not Built in monitoring available with the
Monitoring associated with runtime monitoring development platform
Virtual Multiple options are available and can Need to work with the infrastructure
machines, be customized to meet any user offered by pass providers
Servers, requirement
Storage,
Databases
Integrated May have separate environment and Same environment for all phases
development infrastructure for development testing
environments and debugging
Categories of PaaS
Category Description Examples
I • Developers Prefer to use current tools and locally Force.com, Google,
develop software. LongJump, Magic
• After Compile and test applications are loaded to Software, Microsoft
Cloud NetSuite, TIBCO and
Wavemaker
II • PaaS vendors provide a cloud based development Force.com, Intuit,
environment. Trackvia and wolf
• Browser based access. framework
• Development and testing is done at PaaS provider site.
Web-based • Not written to be web based and Built-In web based and used over
used over internet public internet
• Performance degradation
Software Considerations
• User purchases a software package and license by
paying a one-time fee.
• Support and updates are provided by the vendor
• Saas has no licensing
• Biggest advantage is that software is not installed on
the user’s computer
Vendor Advantages
• The advantages flow both ways.
• vendors get a constant stream of income,
often what is more than the traditional
software licensing setup
• The more resources are used to capacity, the
more the provider can clear as margin.
Limitations
• Technical obstacles to saas have included an
effective, multitenant architecture.
• Software companies are being asked to
become service companies, and the two don’t
necessarily mesh well.
• A business model that is built on selling
licensed software does not easily transform
into a subscription model very cleanly
• Some applications are ideal for saas, others
are not good to use employing an saas model.
SaaS: Driving Forces
• Popularity
– Software Vendor friendly
– Enterprises Friendly
– Plenty of SaaS Platforms
SaaS
A modern implement of
SaaS using an Enterprise
Service Bus and
architected with SOA
components
Mashups
Shows data and supports features from two or
more sources. It requires 3 separate
components.
• An interactive user interface,
• Web services that can be accessed using an
API.
• Data transfer in the form of XML, KML, JSON
Security as a Service(SECaaS)
• Services offered by SECaaS
– Email filtering
– Web content filtering
– Vulnerability management
– Standards and compliance management
– Identifying security risk patterns
– Identity management as a Service
• Two kinds of cloud-based security providers.
– Leading security product vendors
– Emerging small and medium sized security vendors
Web Content filtering
Traditional security VS SECaaS
Criteria Traditional Appliance or software SECaaS
based security
Upfront capital Buy, install and implement servers No upfront expenses
expenses and application
Ease of threat Time consuming and difficult to Efficient threat detection via
detection detect threat on host cloud based servers
Software Each host needed to e updated 24/7, real-time update based on
updates host availability
Operational IT resources are required to manage No need to manage applications
onus hardware, software, database and or software, need to enforce
policies policies at SaaS provider.
IT staff Significant team and talent required Few IT staff required
requirement
Latency Low latency High latency
Control Full control Less control
Green IT More power and cooling required for Shared servers consume less
dedicated security power and cooling
Benefits of SECaaS
• Provides security staff and talent.
• Advanced security tools
• Relevant, timely expertise from provider
• SECaaS can be a business enabler
• specific type of
authentication is not
required
Open Standards for IDaaS
Single sign-on Service
Identity management as a
service(IdMaas)
Phase Task
Phase 1 Assessment and architecture
Phase 2 Password administration
Phase 5 Customizations