The Microtask Queue

Promises don't execute immediately after they resolve. They wait their turn.

The Microtask Queue is a queue that stores callbacks from resolved Promises before they're executed.

Consider:

console.log("A");

Promise.resolve().then(() => console.log("B"));

console.log("C");

The output is:

A
C
B

Even though the Promise resolves immediately, its callback is placed into the Microtask Queue.

JavaScript finishes the current execution first. Only then does it process queued microtasks.

This is the reason why Promise callbacks always run after synchronous code, even when no network request is involved.

📂 API Design Roadmap
┃
┣ 📂 Foundations
┃ ┣ 📂 What is an API?
┃ ┣ 📂 HTTP & HTTPS Fundamentals
┃ ┣ 📂 Request & Response Lifecycle
┃ ┣ 📂 JSON & Data Formats
┃ ┗ 📂 API Design Principles
┃
┣ 📂 REST API Design
┃ ┣ 📂 REST Architecture
┃ ┣ 📂 Resources & Endpoints
┃ ┣ 📂 HTTP Methods (GET, POST, PUT, DELETE, PATCH)
┃ ┣ 📂 Status Codes
┃ ┗ 📂 REST Best Practices
┃
┣ 📂 API Documentation
┃ ┣ 📂 OpenAPI Specification
┃ ┣ 📂 Swagger UI
┃ ┣ 📂 API Reference Documentation
┃ ┣ 📂 Examples & SDKs
┃ ┗ 📂 Versioned Documentation
┃
┣ 📂 Authentication & Authorization
┃ ┣ 📂 API Keys
┃ ┣ 📂 JWT Authentication
┃ ┣ 📂 OAuth 2.0 & OpenID Connect
┃ ┣ 📂 Role-Based Access Control (RBAC)
┃ ┗ 📂 Token Management
┃
┣ 📂 API Security
┃ ┣ 📂 HTTPS & TLS
┃ ┣ 📂 CORS Configuration
┃ ┣ 📂 CSRF & XSS Protection
┃ ┣ 📂 Rate Limiting & Throttling
┃ ┗ 📂 Input Validation & Sanitization
┃
┣ 📂 Advanced API Architectures
┃ ┣ 📂 GraphQL
┃ ┣ 📂 gRPC
┃ ┣ 📂 WebSockets
┃ ┣ 📂 Server-Sent Events (SSE)
┃ ┗ 📂 Event-Driven APIs
┃
┣ 📂 API Performance
┃ ┣ 📂 Pagination
┃ ┣ 📂 Filtering & Sorting
┃ ┣ 📂 Caching Strategies
┃ ┣ 📂 Compression
┃ ┗ 📂 Performance Optimization
┃
┣ 📂 API Reliability
┃ ┣ 📂 Error Handling
┃ ┣ 📂 Retry Strategies
┃ ┣ 📂 Idempotency
┃ ┣ 📂 Circuit Breaker Pattern
┃ ┗ 📂 Health Checks
┃
┣ 📂 API Testing
┃ ┣ 📂 Unit Testing
┃ ┣ 📂 Integration Testing
┃ ┣ 📂 Postman & Insomnia
┃ ┣ 📂 Load Testing
┃ ┗ 📂 Contract Testing
┃
┣ 📂 API Deployment
┃ ┣ 📂 API Gateways
┃ ┣ 📂 Reverse Proxies
┃ ┣ 📂 Docker & Containers
┃ ┣ 📂 CI/CD Pipelines
┃ ┗ 📂 Cloud Deployment
┃
┣ 📂 Monitoring & Observability
┃ ┣ 📂 Logging
┃ ┣ 📂 Metrics Collection
┃ ┣ 📂 Distributed Tracing
┃ ┣ 📂 Prometheus & Grafana
┃ ┗ 📂 API Analytics
┃
┣ 📂 AI-Powered APIs
┃ ┣ 📂 OpenAI API Integration
┃ ┣ 📂 Function Calling
┃ ┣ 📂 Streaming Responses
┃ ┣ 📂 AI Agent APIs
┃ ┗ 📂 Cost & Token Optimization
┃
┣ 📂 Real-World Projects
┃ ┣ 📂 Authentication API
┃ ┣ 📂 E-commerce REST API
┃ ┣ 📂 Payment Gateway API
┃ ┣ 📂 AI Chat API
┃ ┗ 📂 Microservices API Platform
┃
┣ 📂 Practice & Growth
┃ ┣ 📂 Build Public APIs
┃ ┣ 📂 Contribute to API Projects
┃ ┣ 📂 Write API Documentation
┃ ┣ 📂 API Design Reviews
┃ ┗ 📂 Interview Preparation
┃
┗ 📂 Career & Monetization
┣ 📂 Backend Engineer Roles
┣ 📂 API Platform Engineer
┣ 📂 SaaS Development
┣ 📂 API Consulting & Freelancing
┗ 📂 Continuous Learning

👉 Follow this consistently for 2–4 months and you'll be able to design, build, secure, and scale production-ready APIs with confidence.

What Actually Is HTTPS?

HTTPS is HTTP running over TLS (Transport Layer Security).

TLS is responsible for encrypting the communication.

HTTP still handles things like:
🎯 Methods (GET, POST)
🎯 Headers
🎯 Cookies
🎯 Status codes

Before any HTTP data is exchanged, the browser and server perform a TLS handshake.

During this process they:
- Verify the server's identity using its certificate.
- Agree on an encryption algorithm.
- Generate shared encryption keys.

Only after that does the browser send the first HTTP request.

Without TLS, every request and response could be read or modified while travelling across the network.

👉 HTTPS isn't a different protocol. It's HTTP inside an encrypted tunnel.

reactjs-interview-questions

List of top 500 ReactJS Interview Questions & Answers.

Creator: sudheerj
Stars ⭐️: 44,796
Forked by: 10,384

Github Repo:
https://github.com/sudheerj/reactjs-interview-questions

#ReactJS #Interview
➖➖➖➖➖➖➖➖➖➖➖
🚀 More cool repos → @github_repositories_bds
Part of @bigdataspecialist community

How Docker Works

👨‍💻 7 Websites Every CSE Student Should Bookmark

If you're a CSE student, these websites can help you learn, practice, build projects and prepare for placements

1. Roadmap.sh 🗺
• Developer roadmaps for different tech fields
• Great for knowing what to learn next
🔗 https://roadmap.sh/

2. LeetCode 🧩
• Practice DSA and coding problems
• Useful for technical interview preparation
🔗 https://leetcode.com/

3. GitHub 🐙
• Host your projects and contribute to open source
• Build a strong developer profile
🔗 https://github.com/

4. DevDocs 📖
• Documentation for hundreds of programming tools
• Quickly find technical references in one place
🔗 https://devdocs.io/

5. SQLBolt 🗄
• Learn SQL through interactive exercises
• Great for beginners learning databases
🔗 https://sqlbolt.com/

6. Regex101 🔍
• Build, test and debug regular expressions
• Includes explanations and useful debugging tools
🔗 https://regex101.com/

7. Excalidraw ✏️
• Create diagrams, flowcharts and system designs
• Simple, free and easy to use
🔗 https://excalidraw.com/

💾 Save this list. You'll definitely need some of these.


@web_dev_bds