Coding interview preparation
5.75K subscribers
329 photos
47 files
163 links
Download Telegram
Which of the following is not a JavaScript framework or library?
Anonymous Quiz
18%
Polymer
16%
Meteor
18%
jQuery
48%
Cassandra
API Architecture Styles


Choosing the Right API Style Today

APIs come in many flavors, each suited for different needs. SOAP, though reliable for enterprise apps, feels outdated with its XML complexity. RESTful APIs are still the go-to for simplicity and wide adoption, but they can suffer from over- or under-fetching data.

GraphQL is the modern favorite, perfect for getting exactly the data you need—great for front-end flexibility. gRPC shines in high-performance, microservices-heavy environments, while WebSockets handle real-time, low-latency communication brilliantly. Finally, Webhooks are ideal for event-driven applications with asynchronous needs.

In today’s world, GraphQL or RESTful APIs often dominate, but your choice should depend on your app’s specific requirements.
Explanation:
Advance the pointers in such a way that the fast pointer advances two nodes at a time and slow pointer advances one node at a time and check to see if at any given instant of time if the fast pointer points to slow pointer or if the fast pointer’s ‘next’ points to the slow pointer. This is applicable for smaller lists.
Explanation:
Stack follows Last In First Out (LIFO) policy. Piling up of chairs one above the other is based on LIFO, people standing in a line is a queue and if the service is based on priority, then it can be associated with a priority queue. Tatkal Ticket Booking Follows First in First Out Policy. People who click the book now first will enter the booking page first.
Sorry I've forwarded it wrong, here is a complete post:
Forwarded from Web development
5 Valuable Web Development cheat sheets 👆
Please open Telegram to view this post
VIEW IN TELEGRAM
SC15.png
195.6 KB
SQL EXECUTION ORDER

SQL Doesn’t Run the Way You Think It Does!

Most people assume SQL runs top to bottom—
but in reality, the database follows a completely different process.

Here’s what actually happens when you hit Run:

🔹 FROM & JOIN – First, SQL figures out where to pull the data from.
🔹 WHERE – Then, it filters out rows that don’t match your conditions.
🔹 GROUP BY – If needed, it groups the remaining rows together.
🔹 HAVING – Now, it filters those groups (not individual rows).
🔹 SELECT – Finally, it picks the columns you asked for.
🔹 ORDER BY – It sorts the result.
🔹 LIMIT – At the very end, it restricts the output.

Why does this matter?
⤷ You can’t use column aliases in WHERE
because SELECT runs later.
⤷ Filtering after grouping (HAVING)
is less efficient than filtering before (WHERE).
⤷ Understanding this helps you write faster, better queries.

Most analysts assume SQL reads queries like English.
But databases have their own logic—and mastering it makes
you a 10x better analyst!
Python Interview Questions