Once that statement is true, Rails will BE the enterprise. Don't bank on it. (And by that I mean we'll continue to release new versions that at times will be backwards incompatible and require work to upgrade to).
Already is! I've submitted talks a few times about my experiences with Rails in an enterprise environment, no luck. Anyway, We run rails since 2006, we got large and became a bank.
Numbers: 5032 models, 42 gems, 16 submodules, lots of C extensions and eventmachine servers running in threads. From our website to ATM servers, it's everything inside a single rails application. We managed to upgrade from 2.3 to 3.2 in 6 months. Already running 4 (took only a few hours). We just completed our migration from Oracle DB to Postgres.
I would never have thought that was actually possible. A write-up regarding your architecture / challenges / solutions / future plans in a blog post would be extremely interesting.
That is wildly interesting. If you could swing it, you should write up a full post about what that your Rails app looks like after 7 years in production.
I've been postponing writing about this for a long time, mostly because I wanted to talk at railsconf before writing a post (who am I kidding, I just procrastinate a lot), having submitted the talk for the last 3 years without getting in I'll definetly write a long post about it.
Perhaps after receiving feedback on your post, you'll find one oe two aspects that you can refine or drill deeper on and will make a great railsconf talk for next year.
Numbers: 5032 models, 42 gems, 16 submodules, lots of C extensions and eventmachine servers running in threads. From our website to ATM servers, it's everything inside a single rails application. We managed to upgrade from 2.3 to 3.2 in 6 months. Already running 4 (took only a few hours). We just completed our migration from Oracle DB to Postgres.