Cloud Services and Cloud Application Design -
Notes
Unit II – Cloud Services
5 Marks
1. Features of Azure SQL Database
- Fully managed relational database service by Microsoft.
- Scalability & Elasticity – supports dynamic scaling of compute and storage.
- High Availability – built-in redundancy with 99.99% uptime SLA.
- Security – encryption at rest & in transit, firewall rules, advanced threat protection.
- Automatic Backups – point-in-time restore and geo-redundant backup options.
- AI-driven Performance Tuning – query optimization, indexing suggestions.
2. Content Delivery Networks (CDNs)
- Distributed network of servers placed in different geographic regions.
- Stores cached copies of web content (images, videos, scripts).
- Reduces latency, minimizes bandwidth consumption, improves performance.
- Provides availability and security (DDoS protection).
3. BigQuery and HDInsight
Google BigQuery: Serverless, fully-managed data warehouse, supports petabyte-scale analytics,
integrates with Google Cloud AI/ML, pay-as-you-go.
Azure HDInsight: Cloud-based big data service, supports Hadoop, Spark, Hive, HBase. Useful for
analytics, ML, cost-effective and scalable.
10 Marks
1. Deployment & Management Services in AWS
AWS Elastic Beanstalk: PaaS service, supports multiple languages, automatically provisions infra,
focus on code.
AWS CloudFormation: IaC service, uses templates (JSON/YAML), automates provisioning,
supports version control.
Comparison: Beanstalk → App-level, CloudFormation → Infra-level.
2. OpenStack vs CloudStack vs Eucalyptus
Feature OpenStack CloudStack Eucalyptus
API Support OpenStack APIs Native + AWS API AWS-compatible
Popularity High Medium Low
Deployment Complex Simpler Moderate
Best Use Case Enterprise/private cloud Public/private providers AWS hybrid integration
Unit III – Cloud Application Design
5 Marks
1. Main Design Considerations
- Scalability
- Reliability & Fault Tolerance
- Security
- Performance Optimization
- Cost Efficiency
- Multi-tenancy
- Elasticity
2. SOA (Service-Oriented Architecture)
- Applications built as loosely coupled services.
- Communicate via SOAP/REST.
- Role in Cloud: reusability, interoperability, foundation for microservices.
3. Cloud Component Model
- Presentation Layer
- Application Layer
- Data Layer
- Integration Layer
- Security Layer
4. MVC Model
- Model – data & business logic.
- View – user interface.
- Controller – handles input, updates model/view.
- Ensures separation of concerns, scalability, flexibility.
5. SQL vs NoSQL Storage
SQL: Structured, predefined schema, ACID, good for transactional apps.
NoSQL: Schema-less, BASE, good for big data, IoT, real-time apps.
10 Marks
1. Methodologies for Cloud Application Design
- SOA – modular, reusable services.
- MVC – separation of concerns.
- REST – stateless HTTP APIs.
- Microservices – independent deployable units.
- Event-driven – asynchronous processing.
2. Reference Architectures for Cloud Applications
- Three-tier architecture
- Microservices with containers
- Serverless architecture
- Event-driven architecture
- Hybrid cloud architecture
3. IaaS vs PaaS vs SaaS in Application Design
Layer Responsibility Example Role in Design
IaaS Compute, storage, network AWS EC2, Azure VM Full control, custom apps
PaaS Runtime, DB, middlewareGoogle App Engine, Beanstalk Faster dev, less infra mgmt
SaaS Ready-to-use apps Salesforce, Gmail End-user apps, no coding