Version 1.0.0 about rails-api HOT 7 CLOSED

I don't consider it stable enough to be released as 1.0.0. We have some minor issues to solve, some other features/changes to add, and most important, get some good performance benchmarks from the community, to decide about the future of rails-api and consider it a stable 1.0 release.

Thanks!

from rails-api.

If you're adhering to SEMVER then "stability" isn't a factor, production use is and I'm pretty sure it's being used in production. The other part of "1.0" release is the API: Do you consider the API to be stable (as in unmoving) enough? I do, since rails-api is just a set of opinions on-top of rails.

from rails-api.

If it's being used in production by someone, we definitely don't know, but we'd love to for sure. We released rails-api with the idea of getting feedback and performance benchmarks from the community, comparing a normal Rails app with a smaller setup - rails-api. That's why it was reverted from Rails and turned into a gem. In addition to that, I don't consider the API 100% stable enough, things are likely to change, for instance issue #1. Thanks!

from rails-api.

Fair enough.

I'm using it in a few production instances for backends to iOS applications (when Parse.com isn't worth the effort).

from rails-api.

Great to hear that. Perhaps you could help us with some benchmarks if you find it useful and you think it's feasible to do. Cheers

from rails-api.

Absolutely. Anything in particular you want?

from rails-api.

The most interesting performance benchmarks we'd love to see are related to comparing an application running with default Rails stack, and with Rails API, so we'd have a better idea of the performance benefits it can bring (or not).

I know it's a lot of effort to have such benchmarks, so any help towards this is appreciated. Thanks.

from rails-api.