- Full range of CRUD operations, bulk insertions included
- Filtering, Sorting, Pagination, HATEOAS
- JSON and XML Rendering
- Conditional Requests
- Data Integrity and Concurrency Control
- Powerful and extensible Data Validation
- Cache Control
- Document Versioning
- CORS, JSONP
- Rate Limiting
- File Storage
- Logging and the Operations Log
- Mongo Aggregation Framework
- ... and more
For the full story, check out the Eve website.
Why you should pledgeMaintaining and developing new features to projects of this scope takes a considerable amount of time. Also, I do my best to offer support on Stack Overflow and the mailing list, and that takes a lot of time too. So far I have been working on Eve and Cerberus in my free time. I am currently exploring the possibility to dedicate some or all of my working time to Eve, Cerberus and their ecosystem.
If you run a business and is using Eve or Cerberus in a revenue-generating product, it would make business sense to sponsor their development: it ensures the project that your product relies on stays healthy and actively maintained. It can also help your exposure in the Eve community and makes it easier to attract Eve developers.
Of course, individual users are also welcome to make a recurring pledge if either project has helped you in your work or personal projects :)
Things I would be working onWith more time working on to the project there are a lot of things I would like to do including and not limited to:
- Eve-Core: make the separation of concerns between REST and data/validation layers explicit, by splitting the current package. Eve-Core (or Eve-Rest, or whatever) would sit on top, talking to clients and exposing the amazing RESTful features you have been enjoying so far
- Eve-Mongo: move the current Mongo data layer out of core and into its own repository and package. eve-mongo would still be the default layer. Users could easily switch data layer, eventually replacing eve-mongo with eve-sqlalchemy, eve-elastic, eve-neo4js, etc.
- Eve-Validation: explore the possibility of making validation itself a pluggable layer. This might open to the possibility of building custom validation engines.
- Eve-CLI: quick project scaffolding with ready-to-go build & test setups, and a lot more;
- Eve-SDK: client SDKs for Python and other languages. Also improve the existing SDK for .NET; Standardize the SDK API across languages.
- OpenAPI: take Eve-Swagger to the next level. Add support for OpenAPI/Swagger as an alternative to native Eve schema specification;
- Documentation overhaul. One page per feature with in-depth documentation, code snippets, use cases, tutorials;
- Add Cerberus 1.0 support, which would supercharge areas like data validation (schema registry, etc.) and general endpoint configuration;
- Active triaging of GitHub issues;
- Active support on Stack Overflow and the mailing list;
- Test suite overhaul. This is something I have been wanting to do for a very long time. It is strong, but could be way faster, more concise, and readable;
- Official book and training videos;
- Accountability: issue monthly reports on progress made, to all backers;
- And a lot more!
Billing is monthly and you can cancel at any time.