Skip to content

Library vs Framework vs Platform: A Practical Guide to Technology Types

The words get used interchangeably, but they describe very different commitments. A plain-English guide to libraries, frameworks, SDKs, APIs, runtimes and platforms.

rajeshkumar · ·2 min read

“Is React a library or a framework?” is one of those questions that can derail a meeting. The labels matter less than what they tell you about control, lock-in and effort. Here’s a practical way to tell the common technology types apart.

Library: you call it

A library is a collection of code you invoke when you need it. Your application stays in charge of the flow; the library does a specific job and hands control back.

  • Examples: NumPy for numerical arrays, Lodash for JavaScript utilities, React for rendering UI components.
  • Commitment: usually low — you can often swap one library for another in a contained part of the codebase.

Framework: it calls you

A framework provides the overall structure and calls your code at defined points. This is often described as inversion of control: you fill in the blanks the framework leaves for you.

  • Examples: Django (Python), Spring Boot (Java), Next.js (built on React).
  • Commitment: higher — conventions, project layout and lifecycle all come from the framework.

A useful rule of thumb: you call a library; a framework calls you.

SDK: a toolkit for a specific target

A software development kit bundles libraries, tools and documentation for building against a particular platform or service — for example, the AWS SDK for JavaScript or the Firebase SDKs. An SDK is frequently a convenient wrapper around an API.

API: a contract, not code you ship

An API is an interface another system exposes — commonly over HTTP. With a service like the Stripe API or Twilio API, you aren’t installing their code; you’re sending requests to their infrastructure under their terms, pricing and rate limits.

Runtime: where code executes

A runtime (Node.js, the Python interpreter, the JVM) provides the environment that executes your code, including its standard library and package ecosystem.

Platform: an environment you build on

A platform offers a broad set of capabilities you build and run on top of — AWS, Azure, Vercel or GitHub. Platforms often contain many products, each of which may deserve its own listing.

Quick comparison

Type Who’s in control Typical lock-in Example
Library Your code Low Lodash
Framework The framework Medium–high Django
SDK Your code Tied to its target AWS SDK
API The provider Contract & data Stripe API
Platform Shared Often high AWS

Why BestToolsX lets one product have several types

Real products blur these lines. GitHub is a platform, a SaaS product and a web service. That’s why every BestToolsX listing has a primary type plus optional additional types — and why filters adapt to the type you choose. Browse libraries or frameworks to see it in practice.

Share LinkedIn X
Written by
rajeshkumar

Part of the BestToolsX editorial team, writing about software discovery, developer tools and technology catalogs.

Leave a Reply

Your email address will not be published. Required fields are marked *

Keep reading