Skip to main content

What are public, private and hybrid clouds?

Public, Private and Hybrid clouds:
Public Cloud:

Public clouds are the most common type of cloud computing deployment.

The cloud resources (like servers and storage) are owned and operated by a third-party cloud service provider.

Computing in which service provider makes all resources public over the internet. It is connected to the public Internet. 

In a public cloud, you share the same hardware, storage and network devices with other organisations.

Advantages:

  • Low cost
  • No maintenance
  • Scalability
  • Low Failure rate

Disadvantages:

  • Data security and privacy
  • Loss of control
  • Lack of options
  • Lack of customization

Private Cloud:

A private cloud consists of cloud computing resources used exclusively by one business or organisation. 

Physically located at your organisation’s on-site datacenter or it can be hosted by a third-party service provider.

Ability to provide dedicated resources. 

Advantages:

  • High security
  • High performance
  • Easy customization
  • Compliance
  • Better Control

Disadvantages:

  • Costs are substantial in the case of building an on-premise private cloud. 
  • The running cost would include personnel cost and periodic hardware upgrade costs.
  • Under utilization cost
  • Capacity ceiling

Hybrid Cloud:

Hybrid cloud combines on-premises infrastructure a private cloud with a public cloud.

Hybrid clouds allow data and apps to move between the two environments.

    Advantages:

    • greater flexibility
    • more deployment options
    • scale up
    • you can migrate gradually

    Disadvantages:

    • difficult to implement
    • difficult to maintain
    • security breaches to systems
    • complicated operations for organizations



    Comments

    Popular posts from this blog

    Scaled Agile Framework (SAFe)

    The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

    Risk Register

    A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...

    Lessons learned in Project Management

    Lessons learned in Project Management Lessons learned (it may be +ve or -ve) in project management are the knowledge gained during a project that can be used to improve future performance. Lessons learned are documented with solutions to provide future project teams with information that can increase effectiveness and efficiency. Every project manager should be well aware of the impact lessons learned can have on the current and future projects. However, despite knowing the value of lessons learned, not everyone makes full use of them.  The lessons learnt documented using below process flow: 1) Identify: Identify comments and recommendations for use in future project. This is usually done through a project survey that is sent out to all team members. Various questions connected to a project help the participants share their lessons learned.  2) Document: Document and share the findings 3) Analyze: Analyze the finding and find the solution 4) Store: Store in a repository 5) Ret...