i don't know who needs to hear this but your ability to create the reality that you want is directly determined by your willingness to experience its opposite.
- saving money will have you feeling broke while it's actually making you rich.
- setting boundaries will have you feeling alone while you're creating new healthy relationships in your life.
- digging up your trauma will have you feeling broken while it's actually healing you.
- working out has you feeling weak while it's really making you strong.
- learning something new makes you feel dumb while it's making you more intelligent.
your ability to attain the thing that you want is directly correlated with how willing you are to experience its opposite. you have to be ok with being uncomfortable to truly achieve success!
@ashoKumar89 The database layer, So 10× more app servers means 10× more concurrent connections hitting the same database and can cause an overload if there is no adjustment in the connection pooling
@asynctrix The PVC will keep overriding the image at the mount point. The real solution is either to stop mounting persistent storage over application code, or to clean or seed the data inside the volume
Learn Cloud like an engineer, not like someone trying to finish a course.
Most beginners learn like this:
Watch tutorial
→ Learn service
→ Take notes
→ Move on
Engineers learn differently:
Learn the problem before the service
Don’t just ask:
“What is EC2?”
Ask:
“What problem does compute solve?”
Learn how services CONNECT
Route 53
↓
Load Balancer
↓
EC2
↓
RDS
Cloud starts making sense when you understand the flow.
Master networking
• IP
• DNS
• Subnets
• Routing
• NAT
• Firewalls
• Load balancing
You cannot escape networking in Cloud.
BUILD things. Then break them.
Delete a route.
Block a port.
Misconfigure IAM.
Stop an instance.
Then troubleshoot it.
That’s where real learning happens.
Think about FAILURE
Ask:
What if this server dies?
What if traffic becomes 10x?
What if the database goes down?
That’s how you start thinking about architecture.
Learn TRADE-OFFS
More availability → more cost
More performance → more complexity
More security → more restrictions
There is rarely one “perfect” architecture.
Stop memorizing definitions
Don’t just know:
“S3 = Object Storage”
Know:
• When to use it
• When NOT to use it
• How to secure it
• How it scales
• How other services access it
Follow ONE request end-to-end
User
→ DNS
→ CDN
→ Load Balancer
→ Server
→ Database
→ Response
If you can explain that journey clearly, you’re learning Cloud properly.
Courses give you the pieces.
Engineering is understanding how those pieces work together.
What a country.
Young people are actively destroying the roads to unearth metal rods they can sell for quick cash.
The same people destroying the road today will wonder tomorrow when these actions make the road unsafe and end their lives or those of their loved ones.
Yet in the middle of all these, their state governors instead of addressing the poverty and unemployment that is driving this madness in behaviour of their youths, the government is funding mass marriages to produce even more children who will only grow up to participate in this current madness.
What a people. What a government.
A society of lunatics led by lunatics.
@viyancefavour Rare L from you...Usually we, consumers don't benefit,The price stays the same(or rises)while the quality quietly drops across the entire market...Look at Pringles 🤦♂️
The "efficiency" doesn't benefit us; it just normalizes a worse product &protects the company's profit margin
@ulxma Keep being disingenuous.
Your 'nuanced opinion' was 'Bad is better than worse.'
That guy’s own was “I'd rather they die than we all have chaos”
It's the exact same argument.
The fool didn't just mince words & instead said exactly what it means. Own your view with your full chest
I said the song your chairman used is not appropriate for a corporate video. A song sexualising women…you are asking me what I have built in my life. Slave mentality!!
Interviewer:
Your team is planning a high-availability Kubernetes cluster. Describe the Process and Considerations for Designing a High-Availability Kubernetes Cluster.