A collection of terms often used when talking about Jamstack and associated web technologies.
A monolith, or monolithic application, is built and deployed as a single unit. Its user interface, business logic and data access are tightly coupled within one codebase and usually run together on the same server, so a change to any part typically requires the whole application to be rebuilt and redeployed.
Monoliths can be simple to start with, but may become harder to scale, update and reason about as they grow. Jamstack favors decoupling the front end from back-end services, which are often provided through APIs or microservices. A monolith is a software architecture and should not be confused with a monorepo, which describes how code is stored.
You can help us to expand and improve this glossary by creating an issue.