Building Large Scale e-Commerce Systems? 10
Fross asks: "I am Technical Architect at a reasonably large e-commerce firm, which naturally has a very large and active Website, with tens of thousands of registered users, and millions of page hits a month. The time has come to reimplement the old architecture from the ground up, and I'm looking for other (preferably Open Source, or Open Source-friendly) solutions that will give a faster, more scalable, more reliable, easily maintainable solution than the current implementation (which is running under ASP, on IIS of course). I have a fair amount of experience with Perl, some with PHP, but have never used them for something of this size. Does anyone have experience of deploying something this large with these technologies, and can give some valued information on how these solutions cope?"
Check out WebObjects (Score:1)
The big advantage of WebObjects over systems like the ArsDigita Community System, PHP, ASP, and JSP is that it provides nice layers of abstraction. You never have to write SQL (if you don't want to) to get database-backed persistence for your business objects. Your application logic is separate from your business logic which is separate from your presentation logic. It also has nice graphical tools for doing entity-relationship modeling and laying out your dynamic pages and so on.
There are also some great third-party add-ons available for doing things like electronic comerce, wireless access (e.g. WAP), PDF report generation, etc. There is even a large, dynamic developer community.
Of course, WebObjects is a commercial solution, not an Open Source one, but it's a good solution and it's relatively inexpensive considering its capabilities.
Email me if you'd like more information; my company does web application development with WebObjects.
--
Christopher M. Hanson
President
A link for you to check out. (Score:1)
OpenSales [opensales.org]
Hope this helps
Building Large Scale e-Commerce Systems (Score:1)
Completely based on Open Source software, extremely flexible and scalable.
Visit www.akopia.com and www.minivend.com and contact the authors of the software for more information.
why not (Score:1)
Try J2EE on IBM's WebSphere with Oracle or DB2 (Score:2)
One option (Score:2)
Try Contacting a Few Companies (Score:2)
Most folks like to blab about what they've done, so try emailing a few folks, or see what old classmates or fishing buddies the VP's in your company know elsewhere. That'll open doors quickly.
The only thing of real substance I can offer is obvious, but I'll offer it anyway (just to get the ball rolling). Try to modularize everything, and make it generic. Perl, mod-Perl, and PHP all work on NT or *nix, which helps divorce you from a single-vendor situation. The servers can then have any OS or any web server. You could even do a mix in a server farm.
You'll likely need to do something tricky for to bypass some performance bottleneck, but try to keep those tricks simple, with the intent of eventually finding some non-tricky method of getting around that bottleneck.
Re:Large scale systems (Score:2)
Many thanks (Score:2)
fross
Large scale systems (Score:3)
In order to reduce the work, you could use a cisco localdirector or equivalent layer-4 switch instead of the iptables stuff, the rest should basically fit together almost out of the box.
This solution scales very well and handles millions of hits/month. Recommended additions are squid running as an accelerator, since it can absorb a significant number of hits that apache would otherwise have to deal with. However the addition of the Tux in-kernel web stuff on the cluster nodes would probably be an even more preferable solution.
Also recommend dual-cpu machines, they do really well with apache.