Black Jack

Software Developer C# /PHP /Mobile Dev / Web Full Stack Dev/ Data scientist 👨‍💻 || Technical Evangelist || Chelsea fan || Car Ethusiast |

[Mindset Machine  @mindsetmachine]

Opportunities don't happen. You create them

[blue @bluewmist]

You'll never go broke if you sell to:
- Men's lust
- Women's desire for beauty
- Elderly's health
- Cildren's education
- Rich people's fear of loss
- Poor people desire to get rich quick

Understand human nature, and you'll always find a way to succeed.

[New Mentalities @NewMentalities]

The only thing holding you back is your inability to do the work that you know you need to do, without witness or immediate reward for a long enough period of time.

[Aadit Sheth @aaditsh]

This guy literally builds a game using AI in less than 45 minutes

[Ashish Pratap Singh @ashishps_1]

API Gateway Explained:

Imagine you're building a microservices-based application. Each service has its own APIs, handling different parts of your system like authentication, payments, notifications, and more.

As your application grows, the number of APIs increases too. Without the right tools and infrastructure, managing these APIs can quickly become a challenge.

This is where API Gateway comes into play.

It sits between clients (e.g., browsers, mobile apps) and backend services providing a single entry point that manages, optimizes, and secures API calls across your system.

𝐂𝐨𝐫𝐞 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐬 𝐨𝐟 𝐚𝐧 𝐀𝐏𝐈 𝐆𝐚𝐭𝐞𝐰𝐚𝐲:

1. Authentication and Authorization: Ensures only authorized users can access resources via JWT, OAuth, or API keys.

2. Rate Limiting: Prevents abuse and protects backends from DDoS attacks and overloads by limiting requests per user, IP, or API key.

3. Load Balancing: Distributes incoming requests across multiple service instances, preventing bottlenecks and improving response times.

4. Caching: Stores frequently requested responses to reduce backend load and speed up API calls.

5. Request Transformation: Modifies requests/responses on the fly (e.g., convert XML to JSON, modify headers).

6. Service Discovery: Dynamically routes requests to available instances as microservices scale.

7. Circuit Breaking: Prevents cascading failures by returning default responses when services go down.

8. Logging and Monitoring: Offers real-time visibility into API performance, errors, and latency for debugging.

---

♻️ Repost if you found it helpful.

[Navalism @NavalismHQ]

"If you want to make the wrong decision, ask everyone."

@naval

[Gaurav Sen @gkcs_]

Consistent Hashing explained in 1 minute.

Cheers!

#SystemDesign #ConsistentHashing #LoadBalancing

[MarkoNtech @markontechcom]

Essential Git commands for every day usage

[Waigoko Kimengemenge @jrobah]

In Kenya if you work for a tech company then you get a new senior manager who is joing from a Kenyan BANK, just know that you are about to have 100 new problems.

Bankers are the worst people in a tech setting.

[SumitM @SumitM_X]

I often get asked - "How much database knowledge is enough for a backend developer?"

If you're a backend developer looking to learn databases. Learn these 25 topics👇

1. Basic Queries: SELECT, INSERT, UPDATE, DELETE

2. Joins: INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN

3. Indexes: Types, performance impact

4. Normalization & Denormalization: When to use them

5. Transactions: ACID properties, COMMIT, ROLLBACK

6. Stored Procedures & Triggers

7. Query Optimization: EXPLAIN ANALYZE, indexing strategies

8. Sharding & Replication: Scaling databases

9. Partitioning: Horizontal vs. Vertical

10. Locks & Deadlocks: Concurrency control

11. Types of NoSQL Databases: Key-Value (Redis), Document (MongoDB), Column-Family (Cassandra), Graph (Neo4j)

12. Schema Design: Best practices in document-based databases

13. Indexing & Aggregation: Performance tuning in NoSQL

14. CAP Theorem: Trade-offs between consistency, availability, and partition tolerance

15. Eventual Consistency & Strong Consistency

16. Hibernate (Java), JPA

17. Sequelize (Node.js), TypeORM

18. Query performance tuning with ORM

19. Redis vs. Memcached

20. Write-through, Write-back, Write-around Caching

21. Database Query Caching

22. SQL Injection Prevention

23. Role-Based Access Control (RBAC)

24. Encryption at Rest & In Transit

25. Backup & Disaster Recovery

Please Note :
Master SQL first, then NoSQL.

If working in microservices, understanding distributed databases, caching, and event-driven data flow is crucial.

[Mohit Mishra @chessMan786]

3 Symptoms of Bad Code

[Peché Africa 🇿🇦 @pmcafrica]

Chicken can fly, they just lazy

[OLAMIDE 🌸💖 @Olamide0fficial]

We all need to learn this.

[Janty @CFC_Janty]

🚨 Leaked Footage of Pep Guardiola after losing the FA Cup final to Manchester United

[Sahn Lam @sahnlam]

Big O Notation Overview

[Josh @joshtrazyn]

@0xIlyy just one-shot it w/ an alias dawg

[Mr. Rc @rcx86]

Bro dropped a banger and thought we wouldn't notice

[ItsMe @Hitechdigitals]

Thread 🧵

1/ Today, we kickstart our journey south with one destination in mind: Cape Town! 🛣️🇿🇦
@SpaceYaMagari @96Lost_ @alexmwanzo @WillyAbuga @ultramotorske @Kenya_Pretoria @Anto_mbuguaa @victormatara @Mazda_SA @Kalasinga_ @mazdaken @JaMtoka @brokensuit44 @Caradvicekenya

[Ashish Pratap Singh @ashishps_1]

How to Design a Chat Application like WhatsApp:

🔹 Chat Servers - Manages a large number of concurrent WebSocket connections, facilitate real-time communication, and ensure that messages are delivered efficiently between users with minimal latency.

🔹 Load Balancer - Distributes traffic across multiple chat server instances. Uses sticky sessions to ensure clients consistently connect to the same server.

🔹 User Connection Cache -  A fast, in-memory cache (e.g., Redis) that stores user's active connection details, such as the chat server they’re connected to and their last_active timestamp.

🔹 Notification Service - Sends push notifications via providers like FCM or APNS when users are offline.

🔹 Message Queue - Decouples real-time messaging from storage of the messages.

🔹 Message Storage Service - Consumes incoming messages from the Message Queue and persists them in the Message DB for efficient storage and retrieval.

🔹 Group Service - Responsible for handling all group-related functionalities, including creating groups, updating group details and returning list of group members.

🔹 Media Service - Handles the uploading and management of multimedia content, such as images, videos, and audio files.

🔹 Blob Storage - Storage backend for a chat application’s multimedia content (eg., S3).

🔹 CDN - To reduce latency when uploading or downloading multimedia content, files are distributed to locations geographically closer to users via a Content Delivery Network (CDN).

I wrote a detailed article on this system design interview problem. Read it here: https://t.co/b7nEUcloFQ

♻️ Repost to help others in your network.

Subscribe for more such articles every week: https://t.co/kPG9KUxfy6

[Shalini Tewari @maybeshalinii]

In one of my interviews for Backend Developer position, I was asked,

"How would you design an API?"

Here is how you can answer: