Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
out of interest - is devise usable for large scale applications (e.g. Groupon) or better write your own authentication?
yes..devise in used in many large scale applications...moreover it has nothing to do much about scaling as devise will only be used to handle signin/signout/email verification/password management etc which can be also reffered as ONE TIME CONFIGURATION.so even if there are million users...it wont affect your performance as you would be dealing with only one table users.Recenlty i used devise for an application of online students association involving more than 40k on weekly basis..thats a proof
Spree uses devise for authentication, so a lot of the big e-comerce sites are actually running on devise, we never had any issues with it with any of our clients with large user bases. I used other gems from Plataformatec as well, and they are pretty solid. Good luck with your project!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I'm working for a retail company that is implementing an algorithm that determines which one of our warehouses to ship orders from. The logic is going do develop over time and we need to attach the logic version to the order so that our data team can evaluate which algorithm version is the most effective.
Our current code is in a very large rails application, but rather than put the algorithm in there, I'm thinking about building a small gem so the logic is self-contained and the version tagging is clear and easy to use for the data team. The rails logic would then look at the version of the gem and attach that to the order in the database.
One weakness of this approach is that it might be difficult to do concurrent A/B testing. In that case, it would make more sense to have a big class, and each iteration of the algorithm is a separate function, but I worry that someone might make a mistake and it compromises the validity of the data.
Which approach would be best for this problem? Is there another approach that would be better?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am beginner in ROR. I am working on one project. I want to know the better option between for deployment of the app.
My answer will be more conceptual, rather then technical.
This is the first time I hear about Google App Engine in case of Rails. This is mostly a crucial reason, why I would say, that you definitely better go with Heroku.
While you are a beginner, it's better to use the most widely spread solutions and tools. Heroku has a huge history and you can find any answers in the internet very easily. It's well known among rails community and everyone can make a small consultation according to it.
Even if Google App Engine would be better or cheaper (haven't checked it), you shouldn't start such experiments until you have good deploy/rails knowledge.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Which one is the most reliable and the most scalable?
ActionCable or Socket.io?
In order to avoid the opinion based answers please provide some real measured data which prove the hypothesis.
Are there any apps out there in production which were implemented using ActionCable, since ActionCable is out for a year?
Thx
If you are using Rails, ActionCable will be fine. It is currently used on Basecamp and powers their chat and notification features.
This is a large scale application with heaps of daily active users so really you shouldn't be worried about scale. However, if you are talking about millions and millions of active connections, then probably neither is your best option - with the better alternative being Elixir/Erlang (2Million Websocket connections in Phoenix) or even NodeJS.
However in your case if you are using a Rails application, then Actioncable is going to be much easier to implement as it is a feature of Rails and not an external party.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm currently developing a rails app, based on Redmine, using a multitenancy approach. The app it is intended to be used by lots of users (at least I hope so :)), so it is important that it can handle several requests without compromise its performance. Having this in mind, I'm wondering which rails server would suit my needs best. I'm currently using thin, for memory savings purposes, but I'm afraid it is not the best choice for me... I've used unicorn before and I liked it a lot, but it was consuming a lot of memory and I had to change it to another one, but I've noticed that my app is not as fast as it used to be. Any advises? Thanks a lot in advance!
Use Passenger with Apache.
check here
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
For those of you familiar with M. Hartl's RoR Tutorial, do you know if the latest authentication system taught in the book is full proof for a large scale application or would you recommend going in with a ready made authentication systems like Devise or OAuth.
I find the system taught in the book very easy to follow as compared to the ready made systems. I am just not sure if there are any security loopholes in it.
Go with Devise.
Rolling out your own authentication system is great for practice, but many minds beats one, especially when it comes to security.