Skip to main content

Cloud Comparison

Azure vs AWS


Infrastructure As A Service

(AWS) EC2 Instance - elastic cloud compute

Pricing 

1. On demand - pay by hour or pay by second based on the type of instances  (Testing Purpose)

2. Reserved - reserved capacity for One or Three years (For Production, like reserved capacity requirement). The standard reserved instance - upto 72% of the reserved price. The Convertible reserved instances (change the reserved instance to greater capacity like t3 medium to t3 large - upto 54% off on the demand price). Scheduled reserved instance - like fraction of the day , window or month.

3. Spot instances -  instances would be terminated or hibernated if the, not available, price fluctuates  with supply or demand

4. Dedicated - physical EC2 instances, for Compliance or regulatory requirements or licensing requirement

Savings plan - Commit for one or three years   


(Azure) Azure Virtual Machines



Serverless Computing  Function as a service - FAAS , This is an serverless Solution that allows you to write less code, maintain less infrastructure, scale the infrastructure . Serverless computing provides - Auto scaling, High Availability,  Capacity Provisioning , patching

Advantages - Time to market, lower costs , scalable, EVENT Driven, charged only when code is executed.   

AWS serverless -  Lambda, SQS (Simple Queue Service) is an messaging queue that allows you to decouple and scale the application, SNS (Simple Notification Service) send text messages , email and notifications, API Gateway, Dynamo DB (NQSQL DB), S3  

(AWS) Lambda


(Azure) Azure Functions


Coding - 

Function Code 

Function App - A function app provides an execution context in Azure in which your functions run. It is an unit of the deployment and management of one or more functions i.e. an function app can contain one or more functions that can be deployed , managed and scaled together, all share the same pricing model.   The function app resources are the  storage account and , operating systems and the Service plan, For Monitoring you can select the Application Insights  

Folder structure 

What are the Service plan available for the Azure functions ?

Function Trigger - Every Function APP, has exactly one trigger, This trigger causes the function to RUN .  Http Request Trigger (API or Web Hooks) , Timer trigger (Scheduled Tasks) , Blob Storage trigger (data operations) , Queue Trigger , Cosmos DB Trigger, Event Grid Triger , Microsoft Graph Trigger   

The HTTP Request Trigger, can be secured 


Comments

Popular posts from this blog

Hexagonal Architecture (Ports & Adapters Pattern)

Hexagonal Architecture , also known as the Ports and Adapters pattern, is a software design pattern that aims to create a decoupled and maintainable application by separating the core business logic from external concerns (like databases, APIs, and UIs). Structure of Hexagonal Architecture A typical Hexagonal Architecture has three main layers: 1️⃣ Core Domain (Application Logic) This contains the business rules and domain models. It is completely independent of external technologies . Example: If you’re building a banking system , this part would include logic for transactions, withdrawals, and deposits . 2️⃣ Ports (Interfaces) These are interfaces that define how the core interacts with external components. Two types of ports: Inbound Ports (driven by external inputs like APIs, UI, or events) Outbound Ports (used to interact with external services like databases, messaging systems, etc.) 3️⃣ Adapters (Implementation of Ports) These are concrete implementations of the ports, re...

"Action-Oriented, Stakeholder-Focused" MoM Structure

  I. Meeting Header: Meeting Title:  Clear and concise (e.g., "Project X Status Update," "Q3 Planning Meeting"). Date and Time:  Record the date and time the meeting took place. Location/Platform:  Indicate where the meeting was held (e.g., Conference Room A, Zoom). Attendees:  List the names and roles of everyone who attended. Absent:  List the names of key individuals who were invited but did not attend. Meeting Owner : Who was in charge of the meeting ? Document owner : Who is in charge of the documentation ? II. Key Discussion Points (Concise Summary): Purpose:  Briefly summarize the main topics discussed. Format:  Use bullet points for brevity. Content: Decision Points:  Clearly state any decisions that were made. Key Information:  Summarize any crucial information shared. Key Questions : Summarize the key questions that were raised. Open Issues:  Note any issues that remain unresolved. Stakeholder Focus:  Frame the summar...

Frameworks

  I. Frameworks for All Roles (Tech Lead, VP, Individual Contributor): Communication Frameworks: BLUF (Bottom Line Up Front):  For concise and effective communication, especially in emails and reports. SCQA (Situation, Complication, Question, Answer):  For structuring business communications and presentations to present a clear narrative. PAS (Problem, Agitation, Solution):  For a persuasive message. BAB (Before, After, Bridge):  For a persuasive message with a focus on the future. Sparkline:  For persuasive presentation with a focus on change. STAR (Situation, Task, Action, Result):  For structuring behavioral stories, particularly in interviews or performance reviews. Problem-Solving/Decision-Making Frameworks: 5 Whys:  For root cause analysis. Systems Thinking:  For understanding complex systems. The Four Questions:  For a post mortem. Human Factors : For a blame less post mortem. Time Management/Prioritization Frameworks: Eisenhower ...