I did prototype in 2.5 weeks that would have taken months on Apache Tomcat (what they were currently using). And the company was massive, KONE. The content had to handle thousands of requests, work with 2 database times and lots of XML, and be easy to use and expand. I am not there now, but to this day they have always been impress with how fast I was able to code. (I am still buddies with the guys.) BR, Jason
On Mon, 2010-11-29 at 14:46 -0800, Christopher Steel wrote: > +1 > > I agree, Web2py is excellent for low cost prototyping, much less > than .NET and you will actually have something that works... > > I hear that these guys can kick one out in under a month -> > http://experts4solutions.com/ > > ; ) > > Chris > > On Nov 29, 2:51 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > Some political considerations (which may be wrong and off topic and > > improper)... > > > > Here is a problem with external consultants. They make more per hours > > than the average employees. They get hired because of their specific > > expertise to tell you what the boss wants to say but he prefers > > somebody else to say (so he does not take the responsibility for > > saying it). > > > > You cannot win this argument on technical merits. I would dismiss this > > argument and point to Google as a scalability example and it is not > > written in .net. I would address the real concern... you push web2py > > therefore you are a single point of failure. If you leave who takes > > care of this software? Not a problem with .net, they can always hire a > > consultant. > > > > I would stress that using web2py is good for rapid prototyping and it > > will allow the company to have a test product much sooner than > > with .net and at much lower cost. Once the prototype is built you will > > be in a better situation to assess whether web2py or .net is the best > > tool for the job. If you start developing in .net you will have higher > > startup costs and limited flexibility to change the specs. web2py code > > is much more compact and readable than .net code and it will be easier > > to train other people to work with it and learn how it works than > > with .net. Tell them experts4solutions.com can sell them long term > > support contracts and code review. > > > > The scalability bottle neck is the database. Offer something to the > > consultant. .net uses mssql. If he claims mssql scales well for your > > case, web2py will use mssql. > > > > If mssql does not scale well with web2py you have other options and do > > not need to rewrite code. > > > > You can always reuse most of the design (html, js, css, images). > > > > Management costs. I am sure you can make the case it costs less to run > > linux vps than windows ones (although I have no experience with the > > latter). > > > > Massimo > > > > On Nov 29, 12:49 pm, Lorin Rivers <lriv...@mosasaur.com> wrote:> > > Unfortunately, the killing argument is "we know .NET will scale to > > thousands of nodes, blah, blah, blah". > > > > > This from (a guy who's smart and I respect, honestly) who uses his > > > brand-new top-of-the-line 17" MBP to run Windows VMs in Parallels. > > > > > On Nov 29, 2010, at 12:20 , Julio Schwarzbeck wrote: > > > > > > And this without considering "vendor lock-in". web2py can run on a > > > > variety of platforms such as windows, macs. Linux and others, same > > > > goes for the selection of the back-end database. Much more flexibility > > > > under web2py in my opinion and prototyping is much faster in python. > > > > > > On Nov 29, 10:05 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > >> You achieve scalability by replicating the web server behind a load > > > >> balancer. This is documented in the book, chapter 11, using HAProxy. > > > >> All frameworks work the same way in this respect. web2py has no > > > >> intrinsic limitations. The bottle neck is the database connection. All > > > >> frameworks have the same problem. You can replicate the database too > > > >> and web2py supports multiple database clients with Round-Robin. > > > > > >> On a small VPS, web2py in average, should execute one page in 20ms. > > > >> Depending on how many requests/second you need you can determine how > > > >> many servers you need. > > > > > >> web2py apps run on Google App Engine and that means arbitrary > > > >> scalability as long as you can live with the constraints imposed by > > > >> the Google datastore (these limitations will go away as soon as Google > > > >> releases MySQL in the cloud, which they announced some time ago). > > > > > >> Please ask the consultant: which .NET feature makes it scale any > > > >> better than web2py or Rails? If he explains we can address it more > > > >> specifically. > > > > > >> Massimo > > > > > >> On Nov 29, 11:56 am, Lorin Rivers <lriv...@mosasaur.com> wrote: > > > > > >>> The project I'm working on has hired a consultant who is now > > > >>> recommending .Net in place of web2py or even rails. > > > > > >>> What's the 'largest' scale web2py is known to perform well on? > > > > > >>> -- > > > >>> Lorin Rivers > > > >>> Mosasaur: Killer Technical Marketing <http://www.mosasaur.com> > > > >>> <mailto:lriv...@mosasaur.com> > > > >>> 512/203.3198 (m) > > > > > -- > > > Lorin Rivers > > > Mosasaur: Killer Technical Marketing <http://www.mosasaur.com> > > > <mailto:lriv...@mosasaur.com> > > > 512/203.3198 (m)
