Why Pliny?

Rails is one of the most opinionated web frameworks out there, and yet it still leaves a lot of decisions up to the developer: Postgres or MySQL? Minitest or RSpec? Sequential ids or uuids?

Writing APIs for over a decade has made us pretty particular about these. Some choices help prevent production headaches, some help avoid data leaking, and some just doesn't matter – but we still come to a consensus because having standards is important once you're in a team.

Pliny aims to wrap all these decisions and best practices to help Ruby developers write and maintain APIs. It's not the only way to do it, but we think it's a damn fine one.

Next: Getting Started