Cloud Service Models (IaaS,PaaS,SaaS)

Cloud Service Models (IaaS,PaaS,SaaS):

IaaS:

Infrastructure as a service (IaaS) is a type of cloud computing service that offers

essential compute (hardware)
storage
networking resources on demand
middleware (ex: Linux)
OS

IaaS provides services on a pay-as-you-go basis.

Example for IaaS is EC2 (Elastic Compute Cloud) service provided by AWS.

AWS EC2 provides, processers, storages, networking, operating system.

PaaS:

Platform as a service (PaaS) is a complete development and deployment environment in the cloud, with resources that enable you to deliver everything from simple cloud-based apps to sophisticated, cloud-enabled enterprise applications.

Example for PaaS is AWS Elastic Beanstalk provided by AWS, for deploying applications which orchestrates various AWS services, including EC2.

AWS Elastic Beanstalk is an easy-to-use service for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS.

SaaS:

Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet.

SaaS is also known as "On-Demand Software".

Common examples are email, calendaring and office tools (such as Microsoft Office 365), ERP, CRM, Sales, .

SaaS provides a complete software solution which you purchase on a pay-as-you-go basis from a cloud service provider.

Comments

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday? • What will I do today? • What obstacles are impeding my progress? Some people are talkative and tend to wander off into Story Telling . Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. Here are few tips for running a smooth daily meeting: • Everyone should literally stand-up and no one should sit down ...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

High-Tech Yuga

Search This Blog