AWS From Scratch - Part 1 video link ruclips.net/video/rTAwsa-g6kg/видео.htmlsi=owttt8DxDcihTCf- If you are interested, please join below group for free AWS learning groups.google.com/g/payilagam-aws-freecoaching
From my video, you can get 75% knowledge for "AWS Certified Solution Architect - Associate" certification If this is enough to apply AWS intern then 100% you can apply !
Thank you Saravanakumar !!! Payilagam team really appreciate your time and effort for learning AWS from the scratch !!! I was looking for this kind of comment since the Part 1 video was published !!! I am so glad to read your comment !!! Enjoy the part 2 content !!!
To illustrate the differences between Auto Scaling and Elastic Load Balancing (ELB) with a transport analogy, let's compare them to managing a fleet of buses and traffic controllers. ### Scenario: Managing a Fleet of Buses (Auto Scaling) **Auto Scaling**: Imagine you manage a fleet of buses that transport passengers between cities. You want to ensure that there are enough buses to handle the number of passengers at any given time but not too many to avoid unnecessary costs. - **Dynamic Scaling**: During rush hour, you need more buses to accommodate the increased number of passengers. Auto Scaling automatically adds more buses to your fleet when demand increases. - **Scheduled Scaling**: You know that every Monday morning there is a peak in the number of passengers. Auto Scaling can add extra buses to the fleet at scheduled times to meet this expected demand. - **Health Checks**: If a bus breaks down, Auto Scaling detects this and replaces the broken bus with a new one to maintain the desired number of operational buses. - **Cost Efficiency**: During off-peak hours, Auto Scaling removes some buses from service, reducing operational costs while still meeting the passenger demand. ### Scenario: Managing Traffic Controllers (Elastic Load Balancing) **Elastic Load Balancing (ELB)**: Now, imagine you have a team of traffic controllers at various intersections in a city. Their job is to direct traffic to ensure a smooth flow and prevent any intersection from becoming too congested. - **Traffic Distribution**: Traffic controllers direct cars (incoming traffic) to various roads (servers) to ensure that no single road becomes too congested, similar to how an ELB distributes incoming traffic across multiple targets. - **Health Checks**: If a road is blocked due to construction (a server goes down), traffic controllers stop directing cars to that road and instead route them to open, functional roads. ELB regularly checks the health of targets and routes traffic only to healthy ones. - **Types of ELB**: - **Application Load Balancer (ALB)**: A traffic controller who directs cars based on specific criteria, like sending trucks one way and cars another (advanced request routing). - **Network Load Balancer (NLB)**: A traffic controller for highways where speed and minimal delay are crucial (handles TCP/UDP traffic with high performance). - **Gateway Load Balancer (GWLB)**: A controller managing specialized routes for trucks carrying goods to and from distribution centers (managing third-party virtual appliances). ### Combined Use: Fleet of Buses with Traffic Controllers **Combined Use**: Using both analogies together, you can see how they complement each other. Your fleet of buses (Auto Scaling) adjusts the number of buses in operation based on passenger demand, ensuring there are always enough buses but not too many. Meanwhile, your traffic controllers (ELB) ensure that the buses are evenly distributed across various routes to prevent traffic jams and ensure smooth operations. 1. **Auto Scaling**: Automatically adjusts the number of buses in your fleet based on passenger demand, ensuring scalability and cost efficiency. 2. **ELB**: Traffic controllers direct the buses to different routes to balance the load and prevent congestion, ensuring high availability and fault tolerance. ### Summary - **Auto Scaling** is like managing the number of buses in your fleet to match passenger demand, ensuring you have the right number of buses at all times. - **ELB** is like having traffic controllers at intersections to ensure that traffic flows smoothly and no single road becomes too congested. Using both together provides a highly scalable, available, and efficient transport system, just as combining Auto Scaling and ELB does for your AWS architecture.
The primary difference between a Hard Disk Drive (HDD) and a Solid State Drive (SSD) lies in the technology they use to store and retrieve data. Here are the main distinctions between HDDs and SSDs: ### 1. Technology - **HDD (Hard Disk Drive)**: - Uses spinning magnetic disks (platters) to read and write data. - Data is accessed using a read/write head that moves across the spinning platters. - Mechanical components are involved, leading to slower access times. - **SSD (Solid State Drive)**: - Uses flash memory to store data, with no moving parts. - Data is accessed electronically via NAND flash memory. - Faster access times due to the absence of mechanical components. ### 2. Speed - **HDD**: - Generally slower in reading and writing data. - Typical read/write speeds range from 80-160 MB/s, depending on the RPM (Revolutions Per Minute) of the platters. - **SSD**: - Significantly faster read/write speeds. - Typical read/write speeds can exceed 500 MB/s for SATA SSDs, and NVMe SSDs can reach several GB/s. ### 3. Durability and Reliability - **HDD**: - More susceptible to physical damage due to moving parts. - Higher risk of failure from shock or drops. - **SSD**: - More durable and reliable because they have no moving parts. - Better resistance to physical shock and drops. ### 4. Lifespan - **HDD**: - Lifespan can be affected by mechanical wear and tear. - Generally, HDDs have a longer lifespan in terms of data retention if stored properly. - **SSD**: - Lifespan is based on the number of write cycles (wear leveling). - Modern SSDs are designed to handle large amounts of data writing, making their lifespan comparable to HDDs for typical usage scenarios. ### 5. Power Consumption - **HDD**: - Consumes more power due to the mechanical components involved. - Generates more heat and noise. - **SSD**: - Consumes less power, making them more energy-efficient. - Runs cooler and quieter. ### 6. Cost - **HDD**: - Generally cheaper per gigabyte. - Larger capacities are more affordable compared to SSDs. - **SSD**: - More expensive per gigabyte. - Prices are decreasing, but large-capacity SSDs are still more costly than equivalent HDDs. ### 7. Form Factor - **HDD**: - Typically available in 3.5-inch (desktop) and 2.5-inch (laptop) form factors. - **SSD**: - Available in various form factors, including 2.5-inch, M.2, and PCIe NVMe. ### Use Cases - **HDD**: - Suitable for bulk storage, backups, and applications where speed is not critical. - Ideal for archival storage due to its lower cost per gigabyte. - **SSD**: - Ideal for operating systems, applications, and gaming where speed is crucial. - Preferred for laptops and portable devices due to their durability and power efficiency. ### Summary - **HDD**: Uses mechanical parts, is slower, more susceptible to physical damage, consumes more power, and is more cost-effective for large storage capacities. - **SSD**: Uses flash memory, is much faster, more durable, consumes less power, and is more expensive but provides better performance. The choice between an HDD and an SSD depends on the specific needs of the user, such as performance requirements, budget, and storage capacity.
Most expected video. I am a Web developer I. I tried to learn in many sites. I exhausted. Finally your videos give me the grip how to approach the system. Thanks a lot.
route53 concepts venu sir konjam athu oru video va post pannunga sir en comment ku answer pannunga sir please your videos are very interesting so please upload route 53 concept all students are very helpful sir so please post him sir
@@PayilagamChennai tq sir eagerly waiting for your AWS videos so lambda and route 53 cover sir so many students are most awaiting these two topics so eagerly post him sir so thanks for your replying my comment
![Docker Crash Course for Absolute Beginners [NEW]](http://i.ytimg.com/vi/pg19Z8LL06w/mqdefault.jpg)
AWS From Scratch - Part 1 video link
ruclips.net/video/rTAwsa-g6kg/видео.htmlsi=owttt8DxDcihTCf-
If you are interested, please join below group for free AWS learning
groups.google.com/g/payilagam-aws-freecoaching
Bro your aws part 1 and part 2 is enough to get aws internship as a student bro for us is this enough kya?
From my video, you can get 75% knowledge for "AWS Certified Solution Architect - Associate" certification
If this is enough to apply AWS intern then 100% you can apply !
@@PayilagamChennai 75 percent for aws solution architecture wow then from your video I can learn 100% aws cloud practitioner? Bro
I completed the part 1 video, it's awesome😀. It not only helps freshers but also helps to experience people to recall their knowledge.
Thank you Saravanakumar !!!
Payilagam team really appreciate your time and effort for learning AWS from the scratch !!!
I was looking for this kind of comment since the Part 1 video was published !!!
I am so glad to read your comment !!! Enjoy the part 2 content !!!
Most valuable course from valuable person... Romab nandri sir.... ❤❤❤❤... I hope to go ahead and great future ahead...
Thank you so much for your comment !!!
To illustrate the differences between Auto Scaling and Elastic Load Balancing (ELB) with a transport analogy, let's compare them to managing a fleet of buses and traffic controllers.
### Scenario: Managing a Fleet of Buses (Auto Scaling)
**Auto Scaling**:
Imagine you manage a fleet of buses that transport passengers between cities. You want to ensure that there are enough buses to handle the number of passengers at any given time but not too many to avoid unnecessary costs.
- **Dynamic Scaling**: During rush hour, you need more buses to accommodate the increased number of passengers. Auto Scaling automatically adds more buses to your fleet when demand increases.
- **Scheduled Scaling**: You know that every Monday morning there is a peak in the number of passengers. Auto Scaling can add extra buses to the fleet at scheduled times to meet this expected demand.
- **Health Checks**: If a bus breaks down, Auto Scaling detects this and replaces the broken bus with a new one to maintain the desired number of operational buses.
- **Cost Efficiency**: During off-peak hours, Auto Scaling removes some buses from service, reducing operational costs while still meeting the passenger demand.
### Scenario: Managing Traffic Controllers (Elastic Load Balancing)
**Elastic Load Balancing (ELB)**:
Now, imagine you have a team of traffic controllers at various intersections in a city. Their job is to direct traffic to ensure a smooth flow and prevent any intersection from becoming too congested.
- **Traffic Distribution**: Traffic controllers direct cars (incoming traffic) to various roads (servers) to ensure that no single road becomes too congested, similar to how an ELB distributes incoming traffic across multiple targets.
- **Health Checks**: If a road is blocked due to construction (a server goes down), traffic controllers stop directing cars to that road and instead route them to open, functional roads. ELB regularly checks the health of targets and routes traffic only to healthy ones.
- **Types of ELB**:
- **Application Load Balancer (ALB)**: A traffic controller who directs cars based on specific criteria, like sending trucks one way and cars another (advanced request routing).
- **Network Load Balancer (NLB)**: A traffic controller for highways where speed and minimal delay are crucial (handles TCP/UDP traffic with high performance).
- **Gateway Load Balancer (GWLB)**: A controller managing specialized routes for trucks carrying goods to and from distribution centers (managing third-party virtual appliances).
### Combined Use: Fleet of Buses with Traffic Controllers
**Combined Use**:
Using both analogies together, you can see how they complement each other. Your fleet of buses (Auto Scaling) adjusts the number of buses in operation based on passenger demand, ensuring there are always enough buses but not too many. Meanwhile, your traffic controllers (ELB) ensure that the buses are evenly distributed across various routes to prevent traffic jams and ensure smooth operations.
1. **Auto Scaling**: Automatically adjusts the number of buses in your fleet based on passenger demand, ensuring scalability and cost efficiency.
2. **ELB**: Traffic controllers direct the buses to different routes to balance the load and prevent congestion, ensuring high availability and fault tolerance.
### Summary
- **Auto Scaling** is like managing the number of buses in your fleet to match passenger demand, ensuring you have the right number of buses at all times.
- **ELB** is like having traffic controllers at intersections to ensure that traffic flows smoothly and no single road becomes too congested.
Using both together provides a highly scalable, available, and efficient transport system, just as combining Auto Scaling and ELB does for your AWS architecture.
The primary difference between a Hard Disk Drive (HDD) and a Solid State Drive (SSD) lies in the technology they use to store and retrieve data. Here are the main distinctions between HDDs and SSDs:
### 1. Technology
- **HDD (Hard Disk Drive)**:
- Uses spinning magnetic disks (platters) to read and write data.
- Data is accessed using a read/write head that moves across the spinning platters.
- Mechanical components are involved, leading to slower access times.
- **SSD (Solid State Drive)**:
- Uses flash memory to store data, with no moving parts.
- Data is accessed electronically via NAND flash memory.
- Faster access times due to the absence of mechanical components.
### 2. Speed
- **HDD**:
- Generally slower in reading and writing data.
- Typical read/write speeds range from 80-160 MB/s, depending on the RPM (Revolutions Per Minute) of the platters.
- **SSD**:
- Significantly faster read/write speeds.
- Typical read/write speeds can exceed 500 MB/s for SATA SSDs, and NVMe SSDs can reach several GB/s.
### 3. Durability and Reliability
- **HDD**:
- More susceptible to physical damage due to moving parts.
- Higher risk of failure from shock or drops.
- **SSD**:
- More durable and reliable because they have no moving parts.
- Better resistance to physical shock and drops.
### 4. Lifespan
- **HDD**:
- Lifespan can be affected by mechanical wear and tear.
- Generally, HDDs have a longer lifespan in terms of data retention if stored properly.
- **SSD**:
- Lifespan is based on the number of write cycles (wear leveling).
- Modern SSDs are designed to handle large amounts of data writing, making their lifespan comparable to HDDs for typical usage scenarios.
### 5. Power Consumption
- **HDD**:
- Consumes more power due to the mechanical components involved.
- Generates more heat and noise.
- **SSD**:
- Consumes less power, making them more energy-efficient.
- Runs cooler and quieter.
### 6. Cost
- **HDD**:
- Generally cheaper per gigabyte.
- Larger capacities are more affordable compared to SSDs.
- **SSD**:
- More expensive per gigabyte.
- Prices are decreasing, but large-capacity SSDs are still more costly than equivalent HDDs.
### 7. Form Factor
- **HDD**:
- Typically available in 3.5-inch (desktop) and 2.5-inch (laptop) form factors.
- **SSD**:
- Available in various form factors, including 2.5-inch, M.2, and PCIe NVMe.
### Use Cases
- **HDD**:
- Suitable for bulk storage, backups, and applications where speed is not critical.
- Ideal for archival storage due to its lower cost per gigabyte.
- **SSD**:
- Ideal for operating systems, applications, and gaming where speed is crucial.
- Preferred for laptops and portable devices due to their durability and power efficiency.
### Summary
- **HDD**: Uses mechanical parts, is slower, more susceptible to physical damage, consumes more power, and is more cost-effective for large storage capacities.
- **SSD**: Uses flash memory, is much faster, more durable, consumes less power, and is more expensive but provides better performance.
The choice between an HDD and an SSD depends on the specific needs of the user, such as performance requirements, budget, and storage capacity.
Please upload Docker and Kubernetes your AWS video very useful thanks for your support 🙏
Will upload soon
Most expected video. I am a Web developer I. I tried to learn in many sites. I exhausted. Finally your videos give me the grip how to approach the system. Thanks a lot.
I am really glad to read your comment Sabin !
You are welcome !
Bro one subnet for one availability zone , is not correct right. One VPC can contain one or more subnets, like private subnet and public subnet??.
Super expecting more videos
Thank you for your support !!!
Great ❤
Thank you for your support !!!
Thanks ! brother.
You're welcome!
اتمنى اضافة حقل الترجمة ❤
This is lovely.
Thank you !!!
Please cover aws eks and Ecs
Sure, we will put separate video for that !
route53 concepts venu sir konjam athu oru video va post pannunga sir en comment ku answer pannunga sir please your videos are very interesting so please upload route 53 concept all students are very helpful sir so please post him sir
I am glad to see your comment !!!
Sure, we will post about route53 soon
@@PayilagamChennai tq sir eagerly waiting for your AWS videos so lambda and route 53 cover sir so many students are most awaiting these two topics so eagerly post him sir so thanks for your replying my comment
Sir,
Azure devops class eduppeengala..
We are planning for it. We will update later !
Pls explain Dell idrac in Dell server
Can you please make a video on aws project from scratch
Sure, we will try to do it in a separate video.
And, in this AWS Part 1 and 2 contains a small web server project. Hope you reviewed it.
This video enough for get a job?
Please share your job description so that we can compare the required AWS knowledge
Payilagam❤️✨..Could you please tell me what jobs(roles) i can get by practising which are all taught in these two videos (Part 1 and part 2 AWS )?...
Thanks for your question !
I got same question from others also.
I will try to post a separate video for this subject !
link please for this question's answer
@@danysujeeHere it is
ruclips.net/video/_OBQMXz2Mng/видео.htmlsi=bG3QDew6nDbk31fZ
Can i get part 1 video please?
It is already tagged in the comment section
ruclips.net/video/rTAwsa-g6kg/видео.html
Indha course alone is enough for freshers to get a job aa ji???
You can try, if the job requires only the AWS knowledge & small experience.
AWS has future scope?
Yes
Sir Unga video la iruka AWS learn pana job interview crack panalam ah extra learn pananum ah fresher ah aws domain la
If AWS is important in the job description then definitely you can clear the interview with my video.
@@PayilagamChennaiThank you so much brother for your reply.
Part 1 link please
It is pinned in the comment section !
AWS From Scratch - Part 1 video link
ruclips.net/video/rTAwsa-g6kg/видео.htmlsi=owttt8DxDcihTCf-
@@PayilagamChennai Thank you
What are the job openings for me if I complete this playlist and practice......
Kindly check below video for the answer
ruclips.net/video/_OBQMXz2Mng/видео.htmlsi=i-mop7vxz3tYNnw2
@@PayilagamChennai 👍
271 days?
May I know, what 271 days?
@@PayilagamChennai answer to 1:37:55
Thanks ❤ bro
Welcome !