1. ease/speed of programming I think Pylons and Django are both equally easy to grasp.
2. ease of testing TestUnit comes standard in Pylons, functional tests are not that useful, selenium tests are probably better, IMHO. 3. scalability ** DB scaling: SqlAlchemy features will help you here. And there's always memcached / tokyo. ** application-server scaling: mod_proxy to paste is great, but you can go even further by having lighttpd with mod_scgi. Then load balance the lighttpds with HAProxy further if your load is really high. I think you can do the same technique with nginx, but i haven't tried. 4. reliability I have yet to have Paste, Routes, or Beaker to disappoint me. Of course, sqlalchemy and mako template are solid libraries. If you do have problems with Pylons, you know where to ask questions. 5. maintainability The maintainability of your Pylons codes depend on how you write your Python code usually. 6. flexibility I am quite sure Pylons is more flexible than Django. Just plug any kind of Python modules you want. 7. availability of good libraries By using pylons, all of Python's libraries are available to you. Hope that helps. - Didip - On Tue, Jul 14, 2009 at 8:55 AM, DavidG <[email protected]> wrote: > > Hi, > > I am in the midst of developing a "fairly simple" application site, > but where traffic in the real world might be in the "moderate" range > (not low, but not a mega site). > > I have been using python for years, and developed several successful > low-traffic sites with it, using various python web tools from my own, > to myghty, mod_python, pylons...I certainly enjoy the programming > aspect of python, but when you want to get a site up and reliably > running and scaled (and find people to maintain it), perhaps other > factors besides the "language" are more important. > > Question: is pylons ready for prime time? If one were to develop a > moderate-volume, solid site, is python with pylons the "best" thing to > use? How would a pylons site stack up against sites made with php, > rails, java? (btw, I anticipate deploying using Apache and the paste > server via reverse-proxy). > > Here are things to consider: > > 1. ease/speed of programming > 2. ease of testing > 3. scalability > 4. reliability > 5. maintainability > 6. flexibility > 7. availability of good libraries > > I realize these questions have been asked before, but having my > initial "alpha" nearly finished in pylons, doubts are setting in as to > how deployable and scalable in the *real world* this system might be. > I know that *a lot* of sites (especially large ones) use php (which, > as a language, I am less then crazy about). And various java > frameworks (but java is so much work!). And rails? Well, there seems > to be a bit of a controversy as to its performance, flexibility and > scalability. > > Interested in any thoughts folks might have. Thanks. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
