Supporting Someone's Delusions: Why It's Not Always the Right Choice

Encouraging a friend or loved one is an instinctive reaction, but what if their beliefs are not reality-based? In the present age, the "delulu" (short for delusional) is also used in a lighthearted manner to refer to anyone who persists with unrealistic expectations—whether in romance, career, or personal ambitions. While support is needed, blindly backing someone's delusions might actually cause more harm than good in the long term.

Encouragement and optimism are wonderful, but they have boundaries. Encouraging someone's unrealistic expectations without challenging them can set up a false sense of security. When reality finally catches up, the emotional damage is all the greater.

1. False Hope Leads to Harder Falls

Picture this: someone is certain they will land their dream job even though they don't have the skills, qualifications, or preparation. If you continue to tell them, "You got this! No need to prepare, you're perfect for it!"—you may think you're being helpful. But when they get rejected, the hurt and disappointment will be so much worse because they weren't prepared for rejection.

2. Avoiding Reality Can Lead to Bigger Problems

Others overlook red flags in relationships, careers, or life decisions. If an individual feels that their abusive partner loves them even when they are being mistreated all the time, blindly upholding this perception only perpetuates their misery. Rather than uttering "They'll change, just give them time," a real friend would help them see the reality.

3. Emotional Impact: The Aftermath of Failure

When the delusions of someone come crashing down, they feel betrayed—not only by the circumstance, but by those who encouraged them without questioning. They may wonder, "Why didn't anyone warn me?" or feel abandoned when their encouragers suddenly pull away.

How to Support Without Encouraging Delusion

1. Be Honest with Kindness – Rather than agreeing blindly, provide realistic feedback. If a friend is pursuing an unattainable dream, recognize their enthusiasm but also talk about the obstacles. Example: "I love your confidence! Perhaps let's create a backup plan, just in case?"


2. Inspire Growth, Not Dreams – Encourage them to take actual steps towards their aspirations. If they aspire to be a well-known singer but have never had a lesson, encourage them to practice or enroll in classes.

3. Prepare Them for Every Possibility – Expect the best, but also prepare them for the chance of failure. That way, if it doesn't work out, they won't be totally lost.


4. Know When to Step Back – If someone will not listen and is going the way of self-destruction, you can't always rescue them. Occasionally, people must be allowed to fail in order to learn. Stand by them after, but do not intrude on their fantasies.


Support with Limits

Being a supportive family member or friend doesn't imply blindly applauding someone's every idea or decision. Honest, caring, and sometimes harsh truth is true support. Support in the form of encouragement is priceless, but delulu has its boundaries—and when those boundaries are crossed, the fall can hurt all the harder. Rather than supporting delulu thinking, try to guide them toward finding some balance between dreams and reality.


Lab Submission — All 4 Experiments


Experiment 1: Analyze the SPI Model — SaaS, PaaS, and IaaS
Aim
To analyze the SPI (Software, Platform, Infrastructure) model and differentiate between the three primary cloud service delivery methods: Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS).
Theory
Cloud computing service models are categorized under the SPI model, which defines how cloud resources and capabilities are delivered to end-users. Each layer builds on the one below it, offering different levels of abstraction, control, and management responsibility.
1. Software as a Service (SaaS)
SaaS delivers fully functional applications over the internet. The service provider manages everything — servers, storage, networking, OS, runtime, middleware, and the application itself. Users simply access the software through a web browser without worrying about installation, maintenance, or updates.
Definition: Application delivered over the internet, accessible via browser or thin client.
Control: User has no control over infrastructure or platform. Only uses the application.
Management: Entirely handled by the cloud provider.
Examples: Google Workspace (Gmail, Docs), Microsoft 365, Dropbox, Salesforce, Zoom.
Target Users: End users, businesses needing ready-to-use software.
2. Platform as a Service (PaaS)
PaaS provides a platform and environment for developers to build, test, and deploy applications without managing the underlying hardware or OS. The provider handles the infrastructure, OS, runtime, and middleware; the developer focuses only on writing and deploying code.
Definition: A development platform provided over the internet for building and deploying apps.
Control: Developer controls the application and data; provider handles everything below.
Management: Provider manages OS, runtime, servers; developer manages app.
Examples: Google App Engine, Microsoft Azure App Service, Heroku, AWS Elastic Beanstalk.
Target Users: Software developers and DevOps teams.
3. Infrastructure as a Service (IaaS)
IaaS delivers fundamental computing resources — virtual machines, storage, and networking — over the internet. The user has full control over the operating system, applications, and middleware, while the provider manages physical hardware and virtualization.
Definition: Virtualized computing infrastructure provided on demand over the internet.
Control: User controls OS, storage, network configurations, and applications.
Management: Provider manages physical hardware; user manages everything above.
Examples: Amazon EC2, Microsoft Azure VMs, Google Compute Engine, Rackspace.
Target Users: IT administrators, system engineers, enterprises needing flexible infrastructure.
Comparison Table: SPI Model
Feature
IaaS
PaaS
SaaS

Control Level
High
Medium
Low

Manages Hardware
Provider
Provider
Provider

Manages OS
User
Provider
Provider

Manages App
User
User
Provider

Use Case
Build infra
Develop apps
Use software


Conclusion
The SPI model defines three layers of cloud service delivery. IaaS gives maximum control over virtual infrastructure, PaaS abstracts infrastructure to let developers focus on code, and SaaS delivers complete applications requiring no technical setup. Each model serves different users and use cases, and together they form the backbone of modern cloud computing.



Experiment 2: Case Studies on IaaS, PaaS, and SaaS — Virtualization and Cloud Platform Management
Aim
To examine real-world case studies on IaaS, PaaS, and SaaS in order to understand how virtualization is used and how cloud platforms are managed in practice.
Theory
Virtualization is the foundational technology that makes cloud computing possible. It allows a single physical server to run multiple virtual machines (VMs), each with its own operating system and applications. Cloud platform management refers to the tools, policies, and practices used to monitor, scale, secure, and optimize cloud services.
Case Study 1: IaaS — Amazon EC2 (Elastic Compute Cloud)
Amazon EC2 is one of the most widely used IaaS offerings in the world. It provides resizable virtual machines (called instances) in the cloud.
Virtualization Used: AWS uses the Xen hypervisor (and now Nitro) to run multiple virtual machines on physical servers. Each instance is an isolated VM.
How it works: Users select an instance type (e.g., t2.micro, m5.large) based on CPU, RAM, and storage needs. They can start, stop, or terminate instances anytime.
Platform Management: AWS provides the EC2 Management Console, Auto Scaling, Elastic Load Balancing, and CloudWatch for monitoring.
Real Use Case: Netflix uses Amazon EC2 to stream video to millions of users. They scale their server capacity up during peak hours and down during off-peak hours, saving costs.
Key Benefit: Pay-as-you-go pricing; no need to purchase physical hardware.
Case Study 2: PaaS — Google App Engine
Google App Engine is a PaaS solution that allows developers to build and deploy web applications without managing servers or infrastructure.
Virtualization Used: App Engine uses containers (via Google Kubernetes Engine internally) to isolate and run each application. Containers are lightweight compared to VMs.
How it works: Developers write code in supported languages (Python, Java, Node.js, Go) and deploy it directly. App Engine automatically handles load balancing, scaling, and failover.
Platform Management: Google manages runtime, OS patches, database connectivity, and auto-scaling. Developers use the Google Cloud Console and gcloud CLI.
Real Use Case: Snapchat used Google App Engine in its early stages to handle rapid user growth without hiring infrastructure engineers.
Key Benefit: Developers can focus 100% on writing code; no server management needed.
Case Study 3: SaaS — Salesforce CRM
Salesforce is the world's leading Customer Relationship Management (CRM) SaaS platform, used by thousands of businesses globally.
Virtualization Used: Salesforce runs its multi-tenant architecture on virtualized servers where multiple customer organizations share the same infrastructure but are logically isolated.
How it works: Users log in via a web browser and access features like sales tracking, customer data, email automation, and analytics — all managed by Salesforce.
Platform Management: Salesforce manages all layers — hardware, OS, database, application updates — transparently. Users only configure the app through point-and-click tools.
Real Use Case: Coca-Cola uses Salesforce to manage sales operations across 200+ countries, enabling real-time data sharing between field sales teams and headquarters.
Key Benefit: Zero IT overhead for users; automatic updates ensure they always use the latest version.
Key Concepts in Cloud Platform Management
Hypervisor: Software (like VMware ESXi, Microsoft Hyper-V, KVM) that creates and manages VMs on physical hardware.
Containerization: Lightweight virtualization using Docker or Kubernetes where apps run in isolated containers sharing the same OS kernel.
Auto-scaling: Automatically adds or removes resources based on demand.
Load Balancing: Distributes incoming traffic across multiple servers to prevent overload.
Monitoring: Tools like AWS CloudWatch, Azure Monitor track CPU, memory, and application health.
Conclusion
Through these case studies, it is clear that virtualization is the core technology behind all three service models. IaaS exposes VMs directly to users, PaaS uses containers to abstract infrastructure from developers, and SaaS uses multi-tenant virtualization where users share infrastructure without any technical interaction. Cloud platform management tools ensure uptime, performance, and cost optimization at every level.



Experiment 3: Security and Standards — Data Privacy, Access Management, and Interoperability
Aim
To investigate security and standards in cloud computing with a focus on data privacy, access management, and system interoperability.
Theory
Security is one of the most critical concerns in cloud computing. When organizations move their data and applications to the cloud, they must ensure that sensitive information is protected, access is properly controlled, and systems from different providers can work together seamlessly. Cloud security is a shared responsibility between the cloud provider and the customer.
1. Data Privacy in the Cloud
Data privacy refers to the proper handling, processing, and storage of personal and sensitive information. In the cloud, data is often stored in data centers that may be located in different countries, creating legal and regulatory challenges.
Encryption at Rest: Data stored on cloud servers is encrypted so that even if storage media is compromised, data cannot be read. Example: AES-256 encryption used by AWS S3.
Encryption in Transit: Data sent between the user and cloud is encrypted using SSL/TLS protocols to prevent interception.
Data Residency: Some regulations require data to be stored in specific geographic regions. For example, GDPR (General Data Protection Regulation) in Europe requires EU citizen data to remain within EU boundaries.
Data Masking: Sensitive fields (like credit card numbers) are replaced with placeholder values when shown to unauthorized users.
Key Standards: ISO/IEC 27001 (information security), GDPR (EU data protection law), HIPAA (US healthcare data), PCI-DSS (payment card industry).
2. Access Management in the Cloud
Access management ensures that only authorized users and systems can access cloud resources. It involves authentication (verifying who you are) and authorization (defining what you can do).
Identity and Access Management (IAM): Cloud providers like AWS, Azure, and GCP offer IAM systems where administrators define roles, policies, and permissions for users and services.
Multi-Factor Authentication (MFA): Requires users to provide two or more verification factors — e.g., password + OTP — before accessing cloud resources.
Role-Based Access Control (RBAC): Users are assigned roles (e.g., Admin, Developer, Read-Only) and can only perform actions permitted by their role.
Single Sign-On (SSO): Allows users to authenticate once and access multiple cloud services without re-entering credentials. Example: Using a Google account to log into multiple SaaS apps.
Principle of Least Privilege: Users are granted only the minimum permissions necessary to perform their job — reducing risk from insider threats or compromised accounts.
Key Standards: OAuth 2.0 and OpenID Connect for federated identity; SAML (Security Assertion Markup Language) for SSO.
3. System Interoperability in the Cloud
Interoperability means the ability of different cloud systems, services, and providers to work together and exchange data seamlessly. Without interoperability, organizations face vendor lock-in — the inability to switch providers or integrate services.
Open APIs: Standardized Application Programming Interfaces (like REST APIs) allow different cloud services to communicate. Example: A company's AWS-hosted app can connect with a Salesforce SaaS tool via REST APIs.
Open Standards: Standards like OVF (Open Virtualization Format) allow virtual machines to be moved across different hypervisors (VMware, KVM, Hyper-V).
Cloud-to-Cloud Integration: Tools like MuleSoft, Zapier, and AWS EventBridge enable different cloud platforms to exchange data and trigger workflows across providers.
Hybrid Cloud Interoperability: Connecting on-premises data centers with public clouds. Azure Arc and AWS Outposts are examples of tools that extend cloud services to on-premises infrastructure.
Key Standards: TOSCA (Topology and Orchestration Specification), CDMI (Cloud Data Management Interface), OGC (Open Geospatial Consortium).
Cloud Security Shared Responsibility Model
Cloud security is not solely the provider's job. Responsibilities are shared:
Provider's Responsibility: Physical security of data centers, hardware, networking, and hypervisor security.
Customer's Responsibility: Data encryption, access management, application security, and user authentication.
Conclusion
Cloud security requires a multi-layered approach. Data privacy is ensured through encryption and compliance with regulations like GDPR and HIPAA. Access management using IAM, MFA, RBAC, and least privilege principles protects cloud resources from unauthorized access. Interoperability through open APIs and standards prevents vendor lock-in and enables seamless integration across platforms. Together, these elements form a comprehensive cloud security framework.



Experiment 4: Evaluating Amazon Web Services (AWS) — Global Cloud Infrastructure and Service Integration
Aim
To evaluate Amazon Web Services (AWS) as a primary case study for understanding global cloud infrastructure, service integration, and how AWS supports all three cloud service models (IaaS, PaaS, SaaS).
Theory
Amazon Web Services (AWS), launched in 2006, is the world's most comprehensive and widely adopted cloud platform. It offers over 200 fully featured services including compute, storage, databases, machine learning, analytics, networking, security, and more. AWS operates a global infrastructure that allows customers to deploy applications quickly and reliably across the world.
1. AWS Global Infrastructure
AWS has built a massive global infrastructure to ensure high availability, low latency, and disaster recovery.
Regions: A Region is a geographic area containing multiple data centers. As of 2024, AWS has 33+ Regions worldwide including US East (N. Virginia), EU (Frankfurt), Asia Pacific (Mumbai), etc.
Availability Zones (AZs): Each Region has 2–6 Availability Zones — physically separate data centers within the same region, connected by high-speed private fiber. AZs protect against data center failures.
Edge Locations: AWS has 400+ edge locations (Points of Presence) used by Amazon CloudFront (CDN) to cache content closer to end-users, reducing latency.
Local Zones: Extensions of AWS Regions placed closer to large metropolitan areas for ultra-low latency workloads like gaming and live video.
AWS Outposts: Physical AWS hardware installed on-premises in a customer's data center, extending the AWS cloud to their own facility.
2. AWS Core Services
AWS offers services across all three SPI model layers:
IaaS Services:
Amazon EC2 — Virtual machines (instances) in the cloud with various configurations.
Amazon S3 (Simple Storage Service) — Object storage for any type of data; highly scalable and durable.
Amazon VPC (Virtual Private Cloud) — Private, isolated section of the AWS cloud for networking.
PaaS Services:
AWS Elastic Beanstalk — Deploy and manage web applications without managing the underlying infrastructure.
AWS Lambda — Serverless computing; run code without provisioning servers (event-driven).
Amazon RDS (Relational Database Service) — Managed database service for MySQL, PostgreSQL, Oracle, etc.
SaaS-enabling Services:
Amazon WorkSpaces — Cloud-based virtual desktops delivered as SaaS.
Amazon Chime — Video conferencing and messaging platform.
3. AWS Service Integration
One of AWS's biggest strengths is how its services integrate with each other to build complete solutions.
Example Architecture: A web application might use EC2 (compute) + S3 (storage) + RDS (database) + Route 53 (DNS) + CloudFront (CDN) + IAM (security) — all tightly integrated within the AWS ecosystem.
AWS Management Console: A web-based UI to access and manage all services from a single dashboard.
AWS CLI (Command Line Interface): Allows programmatic management of AWS resources via terminal commands.
AWS SDKs: Libraries for Python (Boto3), Java, Node.js, .NET, etc., enabling developers to integrate AWS services directly into their applications.
AWS CloudFormation: Infrastructure as Code (IaC) tool that lets users define and deploy entire cloud architectures using YAML/JSON templates — enabling repeatable, automated deployments.
AWS EventBridge and SNS/SQS: Event-driven services that enable microservices and different AWS services to communicate asynchronously.
4. AWS Security Features
AWS IAM: Manages users, groups, roles, and permissions across all AWS services.
AWS Shield: DDoS (Distributed Denial of Service) protection for AWS applications.
AWS WAF (Web Application Firewall): Filters malicious web traffic to protect applications.
AWS KMS (Key Management Service): Creates and manages cryptographic keys for data encryption.
AWS CloudTrail: Logs all API calls made on an AWS account for auditing and compliance.
5. AWS Real-World Case Studies
Netflix: Uses AWS (EC2, S3, DynamoDB) to stream content to 200+ million subscribers worldwide. AWS allows Netflix to scale to billions of requests per day.
NASA JPL: Used AWS to share data from Mars Rover missions with the public. S3 served terabytes of images globally within hours of landing.
Airbnb: Runs its entire platform on AWS, handling millions of bookings daily using EC2, RDS, and ElastiCache.
Indian Government (MyGov): Uses AWS to host digital governance services accessed by millions of Indian citizens.
6. AWS Pricing Model
Pay-as-you-go: Pay only for what you use with no upfront costs.
Reserved Instances: Commit to 1–3 years for up to 75% discount over on-demand pricing.
Spot Instances: Bid for spare EC2 capacity at up to 90% discount — ideal for batch processing.
AWS Free Tier: New users get 12 months of free access to limited usage of 100+ services including EC2, S3, and RDS.
Conclusion
AWS serves as an exemplary case study for global cloud infrastructure. Its massive network of Regions, Availability Zones, and Edge Locations ensures reliability and low latency worldwide. AWS supports all three SPI service models — providing IaaS (EC2, S3), PaaS (Elastic Beanstalk, Lambda), and SaaS-enabling tools. Its deep service integration, robust security features, and flexible pricing make it the preferred cloud platform for startups, enterprises, and government organizations globally. Understanding AWS provides a solid foundation for understanding cloud computing as a whole.

Post a Comment

0 Comments