ramses
A Python framework that generates RESTful APIs from RAML definitions with support for multiple data stores.
What is ramses?
Ramses is a Python framework that generates RESTful APIs from RAML (RESTful API Modeling Language) definitions. It solves the problem of manually implementing API endpoints by automatically creating them based on your API specification, while providing flexibility in choosing backend data stores like Elasticsearch, PostgreSQL, or MongoDB.
Backend developers and API architects who want to implement specification-first REST APIs in Python with support for multiple database backends.
Developers choose Ramses because it eliminates boilerplate code through automatic API generation from RAML specifications, while maintaining the flexibility to use various data stores through its Nefertari abstraction layer.
Overview
RAML + Elasticsearch / Postgres / Mongodb / Your Data Store™ + Pyramid = RESTful API
Use Cases
Best For
- Rapidly prototyping REST APIs from existing RAML specifications
- Building Python-based APIs that need to support multiple database backends
- Implementing specification-first API development workflows
- Creating RESTful services with Elasticsearch as the primary data store
- Developing APIs that require automatic endpoint generation
- Projects using Pyramid framework that need REST API capabilities
Not Ideal For
- Projects that standardize on OpenAPI/Swagger for API specification and have existing tooling around it
- Teams needing real-time features like WebSockets or GraphQL, as Ramses is focused on RESTful APIs
- Developers seeking a minimal, lightweight framework without the overhead of Pyramid and Nefertari dependencies
Pros & Cons
Pros
Automatically generates complete RESTful endpoints from RAML definitions, eliminating boilerplate code for standard CRUD operations as emphasized in the key features.
Works with Elasticsearch, PostgreSQL, and MongoDB through the Nefertari abstraction layer, allowing seamless backend switching without API redesign, per the project description.
Built on the mature Pyramid web framework, providing a stable and extensible base for web applications, ensuring reliability and customization options.
Promotes clean separation between API design and implementation, enabling teams to define interfaces upfront and generate consistent endpoints, aligning with the philosophy.
Cons
Relies on RAML, which has a smaller community and fewer tools compared to OpenAPI, potentially hindering integrations and long-term support as the ecosystem is less active.
Requires familiarity with both Pyramid and Nefertari, adding a steep learning curve for developers not already invested in these technologies, as indicated by the dependencies.
Automatic generation may not allow fine-grained customization for performance or complex business logic, forcing workarounds or manual overrides in Pyramid.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.