Benefits:
-> Significantly reduce licensing cost -
-> multiple environments provide higher flexibility
-> Inhouse software can be migrated to the cloud.
Its like the shared pool of resources (storage, and processing facilities). Allows user to pay per use instead of paying for all the resources that they may not necessarily use. Its like an on demand software service (IAAS) and allows self service to customers (without the need for the provider to intervene). Resource pooling - computing, network, storage, etc. can be commissioned and decommissioned. Elasticity - dynamically match the need per user demand (for this capacities should be unlimited). Measured service - pay per use must be there.
Cloud Models: - (Most Popular)
IAAS - computing resources - like google colab, AWS,
Sotware - software over internet
Platform- APIs, accomodate cyclical, less predicable demand patterns, seasonal business,
Cloud Deployment Models:
Public Cloud Considerations:
-> Security, noisy neighbours, storage limitations, cost of access transfer, portability - instance types,
Private Cloud:
Internal to Organization, infrastructure can be on premise, difficult to move on cloud when there is a legacy system.
Dedicated Cloud: similar to private cloud, infrastructure can be inhouse.
Virtual private cloud: isolated environment by provider but dedicated. Less security concerns.
Hybrid Cloud: inhouse + cloud infrastructure. Enables smooth migration. No single model, cloud for some applications, whereas some things can be backed up by inhouse infrastructure.
Cloud Washing: Rebrand the old application with the name 'Cloud" - for rebranding /recharging purpose. They dont have any improvemnet over the legacy systems.
My Skill-Set:
Make architectural decisions based on AWS architectural principles and best practices
•Use AWS services to make your infrastructure scalable, reliable, and highly available
•Use AWS managed services to enable greater flexibility and resiliency in an infrastructure
•Indicate how to increase the performance efficiency and reduce costs of infrastructures built on AWS
•Use the AWS Well-Architected Framework to improve architectures that use AWS solution
Governance: cloud application that can be effectively governed and managed. Resource governance and governing computing. Service governance: service oriented applications. security and governance: maintain security. Compliance and government: ensure all govt compliances. Types of governance is bit different from foundational concepts.
Resource Governance: CMP - cloud management platforms for governance: focus on cloud resources like storage, compute, and database services. Service governance provide the ability to access to very fine grained services.
Security and compliance: data is put in the wrong place and is found in compliance audits. There are processes to understand where data can go and who can see. Active governance (automated) is needed to ensure data is not mis-placed. Planning is critical.
Cloud Governance Solution you need: if you meet all reqments, establishing the solution is required:
-> understand the rqments
-> find right tools
-> test cloud governance
-> Determine what you will run long term
USE CASE: defining the action, dont just start with technology unless you understand the reqments, training and hiring should be a part of cloud governance project. People ignore cloud governance and then struggle. Service and resource governance tools are critical. Looking at the market based on requirements. Ensure that tool provider is a solid player, ensure they would exist in the market for long term. Check on traning and tool matter experts. Placing guardrails for your resources, is a good way to govern so tht you dont loose resources to unimportant processes. Governance should adapt to the needs of the businesses.
-> Define - who is responsible for what
-> Integrate the operations processes with other operations processes - continuously improving processes
Cloud is defining how we do Information Technology. Lets take a look at the right information NETWORKWORLD>COM; INFORMATIONWORLD.COM. are latest resources. CLOUDCAST is another podcast on cloud services. Cloud computing is a journey of IT that is economical to use. Those companies leverage cloud computing save a lot of resources.
CC: allows for timesharing the resources and Distributed computing allows to share the workload to many computers in the network.
-> ON demand
-> Self service
-> resource pooling
-> Ubiqutious network access
-> Rapid elasticity
Private cloud (more secure, systems are not shared, govt and finance organizations), public (aws, cheaper, no hardware installation, highly updated and secure), multi (hybrid - broad range of features, not dependent solely on one system, best of both worlds - public and private clouds), community clouds
NIST: national institute of standard and technology
SAAS - google apps, MS 365, etc.
IAAS - storage and services - AWS
PAAS- google app engine - hosting applications, IOS App store.
SAAS providers: salesforce.com, google services, etc. - subscription based, pervasive applications- reaches a lot of users,
-> Significantly reduce licensing cost -
-> multiple environments provide higher flexibility
-> Inhouse software can be migrated to the cloud.
Its like the shared pool of resources (storage, and processing facilities). Allows user to pay per use instead of paying for all the resources that they may not necessarily use. Its like an on demand software service (IAAS) and allows self service to customers (without the need for the provider to intervene). Resource pooling - computing, network, storage, etc. can be commissioned and decommissioned. Elasticity - dynamically match the need per user demand (for this capacities should be unlimited). Measured service - pay per use must be there.
Cloud Models: - (Most Popular)
IAAS - computing resources - like google colab, AWS,
Sotware - software over internet
Platform- APIs, accomodate cyclical, less predicable demand patterns, seasonal business,
Cloud Deployment Models:
Public Cloud Considerations:
-> Security, noisy neighbours, storage limitations, cost of access transfer, portability - instance types,
Private Cloud:
Internal to Organization, infrastructure can be on premise, difficult to move on cloud when there is a legacy system.
Dedicated Cloud: similar to private cloud, infrastructure can be inhouse.
Virtual private cloud: isolated environment by provider but dedicated. Less security concerns.
Hybrid Cloud: inhouse + cloud infrastructure. Enables smooth migration. No single model, cloud for some applications, whereas some things can be backed up by inhouse infrastructure.
Cloud Washing: Rebrand the old application with the name 'Cloud" - for rebranding /recharging purpose. They dont have any improvemnet over the legacy systems.
My Skill-Set:
Make architectural decisions based on AWS architectural principles and best practices
•Use AWS services to make your infrastructure scalable, reliable, and highly available
•Use AWS managed services to enable greater flexibility and resiliency in an infrastructure
•Indicate how to increase the performance efficiency and reduce costs of infrastructures built on AWS
•Use the AWS Well-Architected Framework to improve architectures that use AWS solution
Governance: cloud application that can be effectively governed and managed. Resource governance and governing computing. Service governance: service oriented applications. security and governance: maintain security. Compliance and government: ensure all govt compliances. Types of governance is bit different from foundational concepts.
Resource Governance: CMP - cloud management platforms for governance: focus on cloud resources like storage, compute, and database services. Service governance provide the ability to access to very fine grained services.
Security and compliance: data is put in the wrong place and is found in compliance audits. There are processes to understand where data can go and who can see. Active governance (automated) is needed to ensure data is not mis-placed. Planning is critical.
Cloud Governance Solution you need: if you meet all reqments, establishing the solution is required:
-> understand the rqments
-> find right tools
-> test cloud governance
-> Determine what you will run long term
USE CASE: defining the action, dont just start with technology unless you understand the reqments, training and hiring should be a part of cloud governance project. People ignore cloud governance and then struggle. Service and resource governance tools are critical. Looking at the market based on requirements. Ensure that tool provider is a solid player, ensure they would exist in the market for long term. Check on traning and tool matter experts. Placing guardrails for your resources, is a good way to govern so tht you dont loose resources to unimportant processes. Governance should adapt to the needs of the businesses.
-> Define - who is responsible for what
-> Integrate the operations processes with other operations processes - continuously improving processes
Cloud is defining how we do Information Technology. Lets take a look at the right information NETWORKWORLD>COM; INFORMATIONWORLD.COM. are latest resources. CLOUDCAST is another podcast on cloud services. Cloud computing is a journey of IT that is economical to use. Those companies leverage cloud computing save a lot of resources.
CC: allows for timesharing the resources and Distributed computing allows to share the workload to many computers in the network.
-> ON demand
-> Self service
-> resource pooling
-> Ubiqutious network access
-> Rapid elasticity
Private cloud (more secure, systems are not shared, govt and finance organizations), public (aws, cheaper, no hardware installation, highly updated and secure), multi (hybrid - broad range of features, not dependent solely on one system, best of both worlds - public and private clouds), community clouds
NIST: national institute of standard and technology
SAAS - google apps, MS 365, etc.
IAAS - storage and services - AWS
PAAS- google app engine - hosting applications, IOS App store.
SAAS providers: salesforce.com, google services, etc. - subscription based, pervasive applications- reaches a lot of users,