Scribd
Upload
28 views3 pages

Subhajit Das Cloud Native Development

Uploaded by

das.subhajittribeni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
28 views3 pages

Subhajit Das Cloud Native Development

Uploaded by

das.subhajittribeni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Name: Subhajit Das College ID: O23MSD160112

Subject: Cloud Native Development

1. What Is the Goal of Building a Cloud-Native Application?


The goal of building a cloud-native application is to leverage the advantages of the cloud
computing delivery model to create applications that are scalable, resilient, and flexible. Here
are the key objectives:

1. Increase Efficiency: Cloud-native development brings along agile practices like DevOps
and continuous delivery (CD). Developers use automated tools, cloud services, and
modern design culture to build scalable applications rapidly.
2. Reduce Cost: By adopting the cloud-native approach, companies don’t have to invest in
the procurement and maintenance of costly physical infrastructure. This results in long-
term savings in operational expenditure.
3. Ensure Availability: Cloud-native technology allows companies to build resilient and
highly available applications. Feature updates do not cause downtime and companies
can scale up app resources during peak seasons to provide a positive customer
experience.
4. Deliver Unparalleled Customer Experience and Build Loyalty : Cloud-native apps help
organizations thrive in today’s highly competitive business world by delivering
unparalleled customer experiences.
5. Accelerate Time-to-Market: Faster release of applications is possible following agile
development practices.
6. Improve Operational Efficiency: It helps reduce the overall application development
and deployment costs.
7. Create New Revenue Channels and Increase Profit: Cloud-native applications can help
businesses create new revenue channels and increase profit.
8. Scalability: Cloud-native applications are designed to exploit the scale, elasticity,
resiliency, and flexibility the cloud provides.
9. Future-Proof Software Solutions: This approach allows businesses to create highly
resilient, future-proof software solutions.
10.Shared Ownership Among Software Stakeholders: The goal is always to increase
software delivery velocity and service reliability and to develop shared ownership
among software stakeholders.
2. What Are the Key Criteria Influencing the Choice of a Cloud
Platform?
The choice of a cloud platform is influenced by several key criteria. Here are the top 10 factors
to consider:

1. Understanding Business Needs: Analyze your current infrastructure, applications, and


data to identify the key challenges and opportunities.
2. Cost: Each cloud service provider has a unique bundle of services and pricing
models. Assess your usage patterns to decide which model fits your timeline, budget,
and business model.
3. Performance: Check the performance of the service provider against their SLAs for the
last 6-12 months.
4. Scalability: The ability of the platform to scale up or down based on the demand is
crucial.
5. Security and Compliance: Understanding each CSP’s protection practices will be
important to assess the CSP’s maturity of security processes.
6. Reliability: Ensure your chosen provider has established, documented, and proven
processes for dealing with planned and unplanned downtime.
7. Support System: Consider the support system of the cloud platform.
8. Integration with Existing Systems: The ability of the platform to integrate with existing
systems and technologies is also a key factor.
9. Flexibility: The flexibility of the platform to adapt to changing business needs is
important.
10.Disaster Recovery and Backup: The platform’s disaster recovery and backup capabilities
should be considered.

3. How To Move from Monolithic App Development to Cloud-Native


App Development?
Transitioning from monolithic application development to cloud-native application
development involves several steps. Here’s a general approach:

1. Define Boundaries: Start by defining the boundaries and capabilities of your application.
This will help you understand how much coupling you have within your monolith, which
represents the largest concern in determining how challenging the process will be for
this application.
2. Identify Coupling: Identify the areas of your application that are tightly coupled. These
are the parts of your application that are most likely to cause problems during the
transition.
3. Move to RPC: Transition from a monolithic architecture to a service-oriented
architecture. This involves breaking down your application into smaller, more
manageable services.
4. Define Data Ownership: Each service should have its own database to ensure loose
coupling and high cohesion.
5. Implement Asynchronous Messaging: Use asynchronous messaging to communicate
between services. This decouples the services from each other and allows them to scale
independently.
6. Existing Systems Assessment: Start by assessing the existing technology landscape and
breaking down the monolithic application into microservices.
7. Cloud-Native Architecture Selection: The next step is to select the cloud model
(public/private/hybrid), cloud provider (Azure/AWS/GCP), and container platform that
best meets your business needs.
8. Continuous Integration/Continuous Deployment (CI/CD): Implement CI/CD pipelines
for automated testing and deployment.
9. Monitoring and Logging: Implement comprehensive monitoring and logging to ensure
the health and performance of your applications.
10.Iterative Refactoring: Transitioning to a cloud-native architecture is an iterative process.
Start small, learn from each iteration, and continuously refactor your applications as you
learn more about your domain and the technologies you are using.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy