Skip to main content

Introduction to AWS - Amazon Web Services

Why Cloud?

Cloud computing in simpler terms of having the servers, database servers, hardware far from actual work area which is connected via network and do most of the things through automation, protects data from natural calamities, theft, provision the hardware / software using software remotely and much more..


Key Advantages:

Capital Expenses Vs Variable Expenses


No need to invest huge sum for infrastructure
the work organization doesn't need to pay huge infrastructure costs at first hand,

Additionally the following are the true advantages of cloud computing

Stop Guessing the capacity:

No need to purchase unnecessary hardware other than needed

Increase Speed and Agility

One click adding of servers , processors

Vertical Add and Horizontal Add

GO Global in minutes:

Quick and Auto Deployment made easy

For further details: https://docs.aws.amazon.com/whitepapers/latest/aws-overview/six-advantages-of-cloud-computing.html


Why AWS?

AWS offers a very wide range of services, you can pick the services based on your needs


1) Scale Horizontally
2) Scale Vertically

3) Automation - Auto deployment of code
4) Load balancing
5) Auto scaling
6) Monitoring
7) Alerts
8) Relational Databases
9) NO SQL Databases
10) Data Warehouse
11) Volume of data (Data Lake)
12) Recovery Process
13) Caching
14) Security
15) Auditing

and so on


AWS Pillars



5 Pillars of AWS

Security: Offers granular level of security, traceability, secure transit of data

Reliability: Guarantees the expected action to be performed correctly and consistently by applying the following principles

Auto recovery
Automatically Scale Horizontally to cope up with the growing capacity

Performance Efficiency: Provides the ability to perform the computing efficiently with available resources

Operation Excellence: The ability to support development and run workloads effectively, gain insights from the processes

Anticipate Failure
Learn from Failures 


Cost Optimization : Run the application at low cost, use cloud financial management, measure overall efficiency, analyze and attribute expenditure


Comments

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven