Great Guru Programmers... I really need your advice. I am trying to decide whether to use J2EE, or Rails for development of a online banking solution. My main concern is the ability to integrate with potential banking solutions, which are relentlessly legacy. To cut to the chase...I really just want to know from those of you who are much more aware of Rails abilities if you think that Rails could handle being the platform for an online banking solution, multilingual, with web services, handling potentially 84 million records and 200 million transactions per day while providing a slick and world changing Web 2.0 user interface. That''s what I need. Obviously I have J2EE real case scenarios out there to demonstrate its performance. And please understand that I realize Rails is still new. I would understand if people conceded that Java might be a better solution for my scope for now. I still am planning to utilize Rails for most of my gigs. Thank you. -- ~~~~~~~~~~~~~~~~~~~ D''Andrew "Dave" Thompson http://dathompson.blogspot.com _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Can you use Rails? Yes. Should you use rails? Probably not. Among other reasons, it doesn''t sound like you know Rails well enough to use it in an app like this. Hell, it sounds like you are altogether in over your head. My two cents. On 10/5/05, D''Andrew Dave Thompson <dandrew.thompson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Great Guru Programmers... > > I really need your advice. I am trying to decide whether to use J2EE, or > Rails for development of a online banking solution. My main concern is the > ability to integrate with potential banking solutions, which are > relentlessly legacy. > > To cut to the chase...I really just want to know from those of you who are > much more aware of Rails abilities if you think that Rails could handle > being the platform for an online banking solution, multilingual, with web > services, handling potentially 84 million records and 200 million > transactions per day while providing a slick and world changing Web 2.0 user > interface. That''s what I need. Obviously I have J2EE real case scenarios out > there to demonstrate its performance. > > And please understand that I realize Rails is still new. I would understand > if people conceded that Java might be a better solution for my scope for > now. I still am planning to utilize Rails for most of my gigs. Thank you. > > -- > ~~~~~~~~~~~~~~~~~~~ > D''Andrew "Dave" Thompson > http://dathompson.blogspot.com > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >
>> integrate with potential banking solutionsThis part might be tricky with Rails, but I''m sure your team could do it!>> multilingualThis part is tricky with Rails, but I''m sure your team could do it!> handling potentially 84 million > records and 200 million transactions per day while providing a slick > and world changing Web 2.0 user interface.Rails can do this ... I say go for it and make sure your team gives lots of code back to the community! -----Original Message----- From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Kyle Maxwell Sent: Thursday, 6 October 2005 4:26 PM To: D''Andrew Dave Thompson; rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org Subject: Re: [Rails] Please Advise Java or Rails Can you use Rails? Yes. Should you use rails? Probably not. Among other reasons, it doesn''t sound like you know Rails well enough to use it in an app like this. Hell, it sounds like you are altogether in over your head. My two cents. On 10/5/05, D''Andrew Dave Thompson <dandrew.thompson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Great Guru Programmers... > > I really need your advice. I am trying to decide whether to use J2EE,> or Rails for development of a online banking solution. My main concern> is the ability to integrate with potential banking solutions, which > are relentlessly legacy. > > To cut to the chase...I really just want to know from those of you > who are much more aware of Rails abilities if you think that Rails > could handle being the platform for an online banking solution, > multilingual, with web services, handling potentially 84 million > records and 200 million transactions per day while providing a slick > and world changing Web 2.0 user interface. That''s what I need. > Obviously I have J2EE real case scenarios out there to demonstrate itsperformance.> > And please understand that I realize Rails is still new. I would > understand if people conceded that Java might be a better solution for> my scope for now. I still am planning to utilize Rails for most of mygigs. Thank you.> > -- > ~~~~~~~~~~~~~~~~~~~ > D''Andrew "Dave" Thompson > http://dathompson.blogspot.com > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
I''m with Kyle on this - if you''re asking a Rails mailing list whether you should use Rails for a (presumably) mission-critical application with big security/scalability/integration challenges, you''ll tend to get two types of answers: - "Are you crazy? Nobody''s ever tried this before" - "Of course, Rails can do anything" You certainly shouldn''t expect anything like objective discussion ;-> Somewhere between these two extremes is the truth, but going ahead with Rails could well be a career-defining/limiting/terminating move on your part. I''d be asking yourself these questions, at the very least, before you start: - besides speed of deployment and agility, what does Rails bring to this problem that Java or C++ won''t? If things go very ugly, how are you going to answer the question "Why did you use Rails/Ruby, instead of Java or C++?". I don''t think "Ajax" is going to cut it... - how confident are you that Rails'' support for (your database/s) is robust and feature-complete? - how confident are you that you can actually deploy your application, given the somewhat fluid state of FCGI/SCGI/Apache/lighttpd/... support? - how are you going to manage Rails updates beyond 0.13? What if there''s wholesale changes that break big chunks of your code (as could well be the case)? - how are you going to estimate how long your development is going to take? How are you going to estimate your resource (people and systems) requirements? - how confident are you that Rails will scale in your environment? Dave M. On 10/6/05, Kyle Maxwell <kyle-FOSOgQihYpQjo0HpFSRKWA@public.gmane.org> wrote:> Can you use Rails? Yes. Should you use rails? Probably not. Among > other reasons, it doesn''t sound like you know Rails well enough to use > it in an app like this. Hell, it sounds like you are altogether in > over your head. > > My two cents. > > On 10/5/05, D''Andrew Dave Thompson <dandrew.thompson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Great Guru Programmers... > > > > I really need your advice. I am trying to decide whether to use J2EE, or > > Rails for development of a online banking solution. My main concern is the > > ability to integrate with potential banking solutions, which are > > relentlessly legacy. > > > > To cut to the chase...I really just want to know from those of you who are > > much more aware of Rails abilities if you think that Rails could handle > > being the platform for an online banking solution, multilingual, with web > > services, handling potentially 84 million records and 200 million > > transactions per day while providing a slick and world changing Web 2.0 user > > interface. That''s what I need. Obviously I have J2EE real case scenarios out > > there to demonstrate its performance. > > > > And please understand that I realize Rails is still new. I would understand > > if people conceded that Java might be a better solution for my scope for > > now. I still am planning to utilize Rails for most of my gigs. Thank you. > > > > -- > > ~~~~~~~~~~~~~~~~~~~ > > D''Andrew "Dave" Thompson > > http://dathompson.blogspot.com > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Did you ask any Java mailing lists about this? If not, why not? If you (or your team) already know the limitations of Java well enough (as far as security/scalability/integration -- the big hitters when it comes to a large project) you should probably use that. AJAX-type front-ends can be created with any server-side technology; don''t let that determine what technology you use to handle your mission critical portions of your applications. In short, don''t bet the farm without a lot more research. On 10/6/05, David Mitchell <monch1962-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I''m with Kyle on this - if you''re asking a Rails mailing list whether > you should use Rails for a (presumably) mission-critical application > with big security/scalability/integration challenges, you''ll tend to > get two types of answers: > - "Are you crazy? Nobody''s ever tried this before" > - "Of course, Rails can do anything" > > You certainly shouldn''t expect anything like objective discussion ;-> > > Somewhere between these two extremes is the truth, but going ahead > with Rails could well be a career-defining/limiting/terminating move > on your part. I''d be asking yourself these questions, at the very > least, before you start: > - besides speed of deployment and agility, what does Rails bring to > this problem that Java or C++ won''t? If things go very ugly, how are > you going to answer the question "Why did you use Rails/Ruby, instead > of Java or C++?". I don''t think "Ajax" is going to cut it... > - how confident are you that Rails'' support for (your database/s) is > robust and feature-complete? > - how confident are you that you can actually deploy your application, > given the somewhat fluid state of FCGI/SCGI/Apache/lighttpd/... > support? > - how are you going to manage Rails updates beyond 0.13? What if > there''s wholesale changes that break big chunks of your code (as could > well be the case)? > - how are you going to estimate how long your development is going to > take? How are you going to estimate your resource (people and > systems) requirements? > - how confident are you that Rails will scale in your environment? > > Dave M. > > On 10/6/05, Kyle Maxwell <kyle-FOSOgQihYpQjo0HpFSRKWA@public.gmane.org> wrote: > > Can you use Rails? Yes. Should you use rails? Probably not. Among > > other reasons, it doesn''t sound like you know Rails well enough to use > > it in an app like this. Hell, it sounds like you are altogether in > > over your head. > > > > My two cents. > > > > On 10/5/05, D''Andrew Dave Thompson <dandrew.thompson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Great Guru Programmers... > > > > > > I really need your advice. I am trying to decide whether to use J2EE, > or > > > Rails for development of a online banking solution. My main concern is > the > > > ability to integrate with potential banking solutions, which are > > > relentlessly legacy. > > > > > > To cut to the chase...I really just want to know from those of you who > are > > > much more aware of Rails abilities if you think that Rails could > handle > > > being the platform for an online banking solution, multilingual, with > web > > > services, handling potentially 84 million records and 200 million > > > transactions per day while providing a slick and world changing Web > 2.0 user > > > interface. That''s what I need. Obviously I have J2EE real case > scenarios out > > > there to demonstrate its performance. > > > > > > And please understand that I realize Rails is still new. I would > understand > > > if people conceded that Java might be a better solution for my scope > for > > > now. I still am planning to utilize Rails for most of my gigs. Thank > you. > > > > > > -- > > > ~~~~~~~~~~~~~~~~~~~ > > > D''Andrew "Dave" Thompson > > > http://dathompson.blogspot.com > > > _______________________________________________ > > > Rails mailing list > > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Brock Weaver brockweaver-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org /* you are not expected to understand this */ _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On Oct 6, 2005, at 1:18 AM, D''Andrew Dave Thompson wrote:> Great Guru Programmers... > > I really need your advice. I am trying to decide whether to use > J2EE, or Rails for development of a online banking solution. My > main concern is the ability to integrate with potential banking > solutions, which are relentlessly legacy. > > To cut to the chase...I really just want to know from those of you > who are much more aware of Rails abilities if you think that Rails > could handle being the platform for an online banking solution, > multilingual, with web services, handling potentially 84 million > records and 200 million transactions per day while providing a > slick and world changing Web 2.0 user interface. That''s what I > need. Obviously I have J2EE real case scenarios out there to > demonstrate its performance. > > And please understand that I realize Rails is still new. I would > understand if people conceded that Java might be a better solution > for my scope for now. I still am planning to utilize Rails for most > of my gigs. Thank you.Well, I certainly cannot claim to be a Great Guru Programmer... If you cannot use Rails for some reason and are interested in something agile for Java, we have been using Sails for 8 months on a production application. We are in the process of extracting it now. You can follow our progress on http://www.opensails.org. adam williams
Yes, please don''t go recommending a technology to your client/company if you don''t know enough to answer this yourself, regardless of the technology On 10/6/05, Kyle Maxwell <kyle-FOSOgQihYpQjo0HpFSRKWA@public.gmane.org> wrote:> Can you use Rails? Yes. Should you use rails? Probably not. Among > other reasons, it doesn''t sound like you know Rails well enough to use > it in an app like this. Hell, it sounds like you are altogether in > over your head. > > My two cents.
On 10/6/05, D''Andrew Dave Thompson <dandrew.thompson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Great Guru Programmers... > > I really need your advice. I am trying to decide whether to use J2EE, or > Rails for development of a online banking solution. My main concern is the > ability to integrate with potential banking solutions, which are > relentlessly legacy. > > To cut to the chase...I really just want to know from those of you who are > much more aware of Rails abilities if you think that Rails could handle > being the platform for an online banking solution, multilingual, with web > services, handling potentially 84 million records and 200 million > transactions per day while providing a slick and world changing Web 2.0 user > interface. That''s what I need. Obviously I have J2EE real case scenarios out > there to demonstrate its performance. > > And please understand that I realize Rails is still new. I would understand > if people conceded that Java might be a better solution for my scope for > now. I still am planning to utilize Rails for most of my gigs. Thank you. > > -- > ~~~~~~~~~~~~~~~~~~~ > D''Andrew "Dave" Thompson > http://dathompson.blogspot.com > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >Thoughworks is an enterprise java and .net development company. http://www.thoughtworks.com/ruby.html mentions that Ruby and Rails excel at... "Small to medium Web-based applications with aggressive time-to-market goals" and "So-called ''soft layer'' APIs on hardened transactional systems" It''s rather a given that the core transaction system is not going to be a good idea, but the last point is an interesting perspective. -- Nicholas Van Weerdenburg