A pragmatic take on REST API design arguing that strict REST compliance isn't always necessary. The level of REST maturity should match the expected lifespan and audience of the API. For internal or short-lived APIs with limited clients, a 'RESTish' approximation is often sufficient. Full REST discipline is only warranted for long-lived, widely-consumed public APIs. Developers should invest saved effort into building a richer domain model instead.
1 Impression