CC Unit 3 PPT 1
CC Unit 3 PPT 1
CLOUD COMPUTING
ACADEMIC YEAR 2024-2025
SYMCA - SEMESTER –III
UNIT - III
CLOUD PLATFORMS
Department of MCA
CLOUD PLATFORMS
Azure
▪ Azure is Microsoft’s cloud platform, just like Google has its Google Cloud and
Amazon has its Amazon Web Service or AWS.000.
▪ Generally, it is a platform through which we can use Microsoft’s resources. For
example, to set up a huge server, we will require huge investment, effort, physical
space, and so on.
▪ In such situations, Microsoft Azure comes to our rescue. It will provide us with
virtual machines, fast processing of data, analytical and monitoring tools, and so
on to make our work simpler.
▪ The pricing of Azure is also simpler and more cost-effective. Popularly termed as
“Pay As You Go”, which means how much you use, pay only for that.
Microsoft Azure
▪ Benefits of Microsoft Azure:
1. Hybrid Capabilities: Integrate on-premises and cloud solutions.
2. Cost Management: Flexible pricing and cost management tools.
3. Security: Extensive security offerings and compliance certifications.
4. Global Reach: Datacenters in numerous regions worldwide.
5. Integrated Environment: Seamless integration with Microsoft products
SQL Azure (Azure SQL Database)
▪ Definition: Azure SQL Database is a specific cloud-based relational database service within the
broader Azure platform, based on Microsoft's SQL Server.
▪ Purpose: It is designed to offer a fully managed, scalable, and reliable SQL database as a service
(DBaaS). It's used for storing, querying, and managing relational data in the cloud.
▪ Features:
▪ Managed Service: Microsoft handles database management tasks such as backups, patching,
and scaling.
▪ Scalability: Offers elastic pools, serverless options, and different performance tiers to
accommodate varying workloads.
▪ Security: Built-in features like data encryption (both at rest and in transit), threat detection,
and compliance with various industry standards.
▪ High Availability: Automatic backups, geo-replication, and service-level agreements (SLAs)
that guarantee high uptime.
▪ Integration: Seamlessly integrates with other Azure services, such as Azure Data Factory,
Power BI, and more.
Google App Engine: Architecture, Core Concepts, and
Application Life Cycle
▪Google App Engine (GAE) is a fully managed
platform-as-a-service (PaaS) offering from Google
Cloud that allows developers to build, deploy, and scale
applications without worrying about underlying
infrastructure. Here's a breakdown of its architecture,
core concepts, and application life cycle:
Architecture
▪ Frontend and Backend Services:
▪ Frontend Services: Handle HTTP(S) requests, user interactions, and routing. App
Engine automatically manages load balancing and scaling for these services.
▪ Backend Services: Perform heavy computational tasks, background processing, and
long-running operations. Backend services can be configured with different scaling
types (automatic, manual, or basic) to optimize performance and cost.
▪ App Engine Environment:
▪ Standard Environment: Supports specific languages (e.g., Python, Java, Node.js,
PHP, and Go) with automatic scaling and integrated development tools. It uses a
sandboxed environment with restrictions to ensure security and efficient resource
utilization.
▪ Flexible Environment: Supports a broader range of programming languages and
allows more customization. It runs on Docker containers on Google Compute Engine,
providing more control over the environment while still offering managed scaling.
Architecture
▪ Datastore and Services:
▪ Google Cloud Datastore: A NoSQL database that provides scalable, flexible storage
for applications.
▪ Google Cloud Storage: For storing and serving large amounts of unstructured data.
▪ Google Cloud SQL: A fully managed relational database service.
▪ Task Queues: Manage background tasks and asynchronous processing.
▪ Memcache: A distributed caching system to speed up data retrieval.
▪ App Engine Modules:
▪ Modules (or services) allow you to structure an application as a set of microservices
with different settings, scaling configurations, and runtimes.
Core Concepts
1. Instance Management:
•Automatic Scaling: App Engine automatically starts, stops, and scales instances based on request
load.
•Manual Scaling: Developers can specify a fixed number of instances that run continuously.
•Basic Scaling: Instances are created when requests arrive and are terminated when idle.
2. Versioning:
•Each deployment is assigned a version, allowing developers to roll out updates gradually,
manage traffic distribution, and roll back changes if necessary.
3. Traffic Splitting:
•Distributes incoming traffic across different versions of an app to enable A/B testing, gradual
rollouts, or blue-green deployments.
4.Security:
•Integrated with Google Cloud Identity and Access Management (IAM) for fine-grained access
control.
•Support for SSL/TLS for secure communication.
5. Monitoring and Logging:
•Integration with Google Cloud Monitoring and Cloud Logging for real-time insights, performance
metrics, and error tracking.
Application Life Cycle
•Development:
•Developers write code using supported languages and frameworks,
using App Engine’s SDKs for local testing and debugging.
•Deployment:
•The application is deployed to App Engine using the.
•The deployment is versioned, and developers can manage traffic routing between different versions.
•Scaling and Load Management:
•As traffic increases, App Engine automatically scales instances to handle the load. Conversely,
it scales down when demand decreases to optimize resource usage.
•Monitoring and Optimization:
•After deployment, the app is monitored using Google Cloud Monitoring and Cloud Logging.
•Developers can optimize performance by adjusting instance settings, caching strategies,
and database queries.
•Updates and Rollbacks:
•New versions of the application can be deployed without downtime. Traffic splitting and
version management allow for smooth transitions between versions.
•If issues arise, developers can quickly roll back to a previous version.
•Maintenance and Decommissioning:
•App Engine handles patching and maintenance of the underlying infrastructure automatically.
•When an application is no longer needed, it can be decommissioned by disabling or deleting
the associated App Engine service.
Salesforce.com
▪ Salesforce.com
▪ Salesforce.com is a cloud-based customer relationship management (CRM) platform that provides tools
for managing customer interactions, sales, marketing, and service processes. Here’s an overview of its
architecture, core concepts, and application life cycle:
▪ Architecture
▪ Multi-Tenant Cloud Architecture:
▪ Salesforce operates on a multi-tenant architecture where multiple customers share the same infrastructure but have their data
and configurations isolated from each other.
▪ Metadata-Driven Development:
▪ Applications and customizations in Salesforce are defined as metadata. This allows for easy upgrades, scalability, and
maintenance since changes are abstracted from the actual code.
▪ API-Centric:
▪ Salesforce is highly API-driven, enabling integration with other systems and custom applications. Key APIs include the REST
API, SOAP API, Bulk API, and Streaming API.
▪ Force.com Platform:
▪ A Platform-as-a-Service (PaaS) offering that allows developers to build custom applications on top of Salesforce. It includes
tools like Apex (a proprietary programming language), Visualforce (UI framework), and Lightning Components.
▪ AppExchange:
▪ An online marketplace for third-party applications and components that can be integrated with Salesforce. These apps are
built by partners and can extend Salesforce's functionality.
THANK YOU !!