Renzop

🇵🇪

[Renzop @rpillmans]

@babyofshadows Tírate grabando

[Md Riyazuddin @riyazmd774]

Peaky Blinders, Stranger Things, Money Heist, The Queen’s Gambit, and Narcos are Netflix shows that need no introduction.

Here are 20 hidden Netflix gems to watch this weekend you might not know about...🔖

[Interesting STEM @InterestingSTEM]

Software Architectural Patterns

[System Design Codex @ProgressiveCod2]

Load Balancers are literally 100 times better than a good old traffic signal.

They can handle millions of incoming requests, distribute traffic between servers and generally keep things smooth with minimal configuration.

Why?

Because Load Balancers can use some really nice algorithms on the fly.

Broadly, there are two categories of these algorithms:

✅ Static

- Round Robin
- Sticky Round Robin
- Hash
- Weighted Round Robin

✅ Dynamic

- Least Connections
- Least Response Time

Let’s look at each algorithm in a little more detail

👉 Round Robin

- Requests are distributed sequentially across a group of servers.

- No guarantee that multiple requests from a user will reach the same instance.

👉Sticky Round Robin

- A better alternative to round-robin

- Different requests from the same user go to the same instance

👉 Hash-Based

- The algorithm distributes requests based on the hash of a key value.

- The key can be the IP address or the URL of the request

👉 Weighted Round Robin

- Each server gets a weight value.

- This value determines the proportion of traffic.

- Servers with higher weight receive more traffic. Good for setups having servers at different capacity levels

👉Least Connections

- A new request is sent to the server instance with the least number of connections.

- The number of connections is determined based on the relative compute capacity of a server

👉Least Response Time

- A new request is sent to the server with the lowest response time in order to minimize the overall response time.

- Good for cases where response time is critical.

===

That's all for now!

If you enjoyed this explanation of Load Balancers and the various algorithms they use, what are you waiting for?

- Test the Load Balancing of the LIKE button
- REPOST to share the information with others
- BOOKMARK for future reference
- Follow me for more stuff like this.

[Security Trybe @SecurityTrybe]

Linux Cheat Sheet

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝘆 𝗶𝘀 𝘁𝗵𝗲 𝗧𝘄𝗲𝗹𝘃𝗲-𝗙𝗮𝗰𝘁𝗼𝗿 𝗔𝗽𝗽 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁?

It explains many well-tested architectural patterns and best practices that can be applied to software-as-a-service (SaaS) apps. These recommended practices allow apps to be developed with resilience and portability for online deployment.

The Twelve Factors:

𝗜. 𝗖𝗼𝗱𝗲𝗯𝗮𝘀𝗲
One codebase tracked in revision control, many deploys

𝗜𝗜. 𝗗𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗶𝗲𝘀
Explicitly declare and isolate dependencies

𝗜𝗜𝗜. 𝗖𝗼𝗻𝗳𝗶𝗴
Store config in the environment

𝗜𝗩. 𝗕𝗮𝗰𝗸𝗶𝗻𝗴 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀
Treat backing services as attached resources

𝗩. 𝗕𝘂𝗶𝗹𝗱, 𝗿𝗲𝗹𝗲𝗮𝘀𝗲, 𝗿𝘂𝗻
Strictly separate build and run stages

𝗩𝗜. 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀
Execute the app as one or more stateless processes

𝗩𝗜𝗜. 𝗣𝗼𝗿𝘁 𝗯𝗶𝗻𝗱𝗶𝗻𝗴
Export services via port binding

𝗩𝗜𝗜𝗜. 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝗰𝘆
Scale out via the process model

𝗜𝗫. 𝗗𝗶𝘀𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆
Maximize robustness with fast startup and graceful shutdown

𝗫. 𝗗𝗲𝘃/𝗽𝗿𝗼𝗱 𝗽𝗮𝗿𝗶𝘁𝘆
Keep development, staging, and production as similar as possible

𝗫𝗜. 𝗟𝗼𝗴𝘀
Treat logs as event streams

𝗫𝗜𝗜. 𝗔𝗱𝗺𝗶𝗻 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀
Run admin/management tasks as one-off processes

Also, in the book "Beyond the 12 Factor App", Kevin Hoffman presents 𝗻𝗲𝘄 𝗴𝘂𝗶𝗱𝗲𝗹𝗶𝗻𝗲𝘀 that build on the original 12 factors but include elements such as telemetry and security:

1. One codebase, one application
2. API first
3. Dependency management
4. Design, build, release, and run
5. Configuration, credentials, and code
6. Logs
7. Disposability
8. Backing services
9. Environment parity
10. Administrative processes
12. Port binding
13. Stateless processes
14. Concurrency
15. Telemetry
16. Authentication and authorization

Image credits: DZone.

#technology #softwareengineering #programming #cloudcomputing #techworldwithmilan

[Dr Milan Milanović @milan_milanovic]

𝗛𝗼𝘄 𝘁𝗼 𝗟𝗲𝗮𝗿𝗻 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻?

If you're working as a software developer and you want to move towards a software architect role, or you're preparing for coding interviews for more senior roles, systems design is an important skill you need to have. Without knowing it, you will have a hard time designing new software systems and understanding existing ones.

System design refers to 𝘁𝗵𝗲 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗼𝗳 𝗱𝗲𝗳𝗶𝗻𝗶𝗻𝗴 𝗮 𝘀𝘆𝘀𝘁𝗲𝗺'𝘀 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀. Architecture, modules, components, interfaces, and data are a few examples of these aspects. The process of defining, creating, and designing systems that suit the particular objectives and requirements of an organization is what you need to understand when it comes to system design.

To understand system design, you will need to know the following:

𝟭. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘃𝘀 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆
𝟮. 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 𝘃𝘀 𝗧𝗵𝗿𝗼𝘂𝗴𝗵𝗽𝘂𝘁 𝗮𝗻𝗱 𝗔𝘃𝗮𝗶𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝘃𝘀 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 (𝘄𝗶𝘁𝗵 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀)
𝟯. 𝗔𝘃𝗮𝗶𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀
𝟰. 𝗕𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗷𝗼𝗯𝘀
𝟱. 𝗗𝗼𝗺𝗮𝗶𝗻 𝗡𝗮𝗺𝗲 𝗦𝘆𝘀𝘁𝗲𝗺𝘀
𝟲. 𝗖𝗗𝗡𝘀
𝟳. 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿𝘀
𝟴. 𝗖𝗮𝗰𝗵𝗶𝗻𝗴
𝟵. 𝗔𝘀𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗶𝘀𝗺
𝟭𝟬. 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀
𝟭𝟭. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗮𝗻𝘁𝗶𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀
𝟭𝟮. 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴
𝟭𝟯. 𝗖𝗹𝗼𝘂𝗱 𝗱𝗲𝘀𝗶𝗴𝗻 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀

To learn this, here are some 𝗯𝗼𝗼𝗸𝘀 where you can start learning:

𝟭. 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄

One of the best books in this field, where you will learn how to design systems such as web crawlers or even YouTube.

Link: https://t.co/FS1xScwM1a

𝟮. 𝗗𝗲𝘀𝗶𝗴𝗻𝗶𝗻𝗴 𝗗𝗮𝘁𝗮-𝗜𝗻𝘀𝗲𝗻𝘀𝗶𝘁𝗶𝘃𝗲 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀

In this book, the author writes about different technologies used to store and process data. By reading it, you will gain insight into different algorithms used in the database world.

Link: https://t.co/FeB1UiM2qp

𝟯. 𝗛𝗲𝗮𝗱 𝗙𝗶𝗿𝘀𝘁 𝗗𝗲𝘀𝗶𝗴𝗻 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀

A great book on OO design patterns, written in a simple style with examples in Java.

Link: https://t.co/SiqEzg1Fug

𝟰. 𝗖𝗿𝗮𝗰𝗸𝗶𝗻𝗴 𝘁𝗵𝗲 𝗖𝗼𝗱𝗶𝗻𝗴 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄

It is a general-purpose coding interview book where the author shares her insights into programming interviews at big tech companies like Microsoft and Google. It covers all basic topics like algorithms, data structures, SQL, etc.

Link: https://t.co/j295Zvs8KW

𝟱. 𝗙𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀 𝗼𝗳 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲

As System Design is related to Software Architecture, this book will give you an introduction to how to architect software systems. This book examines architecture patterns, components, soft skills, modernity, architecture as engineering, and many more.

Link: https://t.co/nhNA8xXvDr

Check the System Design Roadmap in the image (by roadmap .sh).

#softwareengineering

[Alex Xu @alexxubyte]

Explaining 9 types of API testing. The method to download the high-resolution PDF is available at the end.

🔹 Smoke Testing
This is done after API development is complete. Simply validate if the APIs are working and nothing breaks.

🔹 Functional Testing
This creates a test plan based on the functional requirements and compares the results with the expected results.

🔹 Integration Testing
This test combines several API calls to perform end-to-end tests. The intra-service communications and data transmissions are tested.

🔹 Regression Testing
This test ensures that bug fixes or new features shouldn’t break the existing behaviors of APIs.

🔹 Load Testing
This tests applications’ performance by simulating different loads. Then we can calculate the capacity of the application.

🔹 Stress Testing
We deliberately create high loads to the APIs and test if the APIs are able to function normally.

🔹 Security Testing
This tests the APIs against all possible external threats.

🔹 UI Testing
This tests the UI interactions with the APIs to make sure the data can be displayed properly.

🔹 Fuzz Testing
This injects invalid or unexpected input data into the API and tries to crash the API. In this way, it identifies the API vulnerabilities.

Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐜𝐡𝐞𝐚𝐭 𝐬𝐡𝐞𝐞𝐭. After signing up, find the download link on the success page: https://t.co/Zx9BH4M3Qm

[Renzop @rpillmans]

@carlaconwifi @RecuerdameBot @RecuerdameBot cada jueves a las 5pm, horario Peru

[Renzop @rpillmans]

@madzadev @SaveToBookmarks

[Renzop @rpillmans]

@pablom_m @SaveToBookmarks

[Renzop @rpillmans]

@ChacoteroPeru @DescargarBot

[Renzop @rpillmans]

@romanhelipc Miserable abusivo

[Renzop @rpillmans]

@MinCulturaPe @EmbSuizaPeru Algún aprendizaje. No es el único edificio emblemático en mal estado. 💡 💡

[Renzop @rpillmans]

@tromepe Chupapis

[Renzop @rpillmans]

@revolucytierra @RecuerdameBot a las 5 pm

[Renzop @rpillmans]

@blindma1den @SaveToBookmarks

[badger @badger69420]

My first day at work