Archive for June, 2007

19
Jun
07

AspDotNetStorefront Scalability

With the recent buzz and excitement around AspDotNetStorefront (ASPDNSF), and not to mention their amazing growth from a less than $100 shopping cart to what they are now, one can only wonder how far can this thing go? The moon? The stars? Well, it all depends on what you want to accomplish with it, and how scalable ASPDNSF is.

A little side note on the staff/team at ASPDNSF, who I had the pleasure of meeting (including the CEO – Rob Anderson) at a recent event in El Segundo hosted by them and Interprise Solutions (since they are partnered and “integrated” now). Overall, a great team and very energetic. Their hightened participation with the developer community has taken the Open Source model, to a certain extent, and brought it to the .NET community – offering their entire source code to customize as you please is a big plus. In fact, sending them recommendations for enhancements is encouraged, which is great. Keep on keeping on ASPDNSF!

Now, back to scalability… According to Wikipedia’s entry on scalability: scalability is a desirable property of a system, a network, or a process, which indicates its ability to either handle growing amounts of work in a graceful manner, or to be readily enlarged. So what does that mean for ASPDNSF?

If anything, the main area of focus for scalability concerns is with order processing – how many orders can the site process concurrently and continue to stay online. I cannot throw out any numbers because every environment is different – from hardware to bandwidth selection, and Windows to IIS optimizations.

ASPDNSF can scale very well in a Web farm and meet fairly high demands on order processing. For example, in a 4 server Web farm one can easily handle 2-3,000 orders per day and around 2-3 million hits. Selecting a good load balancer is critical, as well as configuring it right to handle requests gracefully enough so IIS can keep running smoothly.

These numbers are not entirely aligned with an “enterprise level” site (e.g. Amazon, Eastbay etc.), something Commerce Server 2007 is designed to scale and handle very well, but they are definitely ideal for small to mid-size businesses. ASPDNSF IS, which is still in its “birth phase”, offers more room for growth since the Web admin system has been removed and now entirely resides using the IS client-based Windows applications (this is very similar to the strategy Commerce Server 2007 has taken).

Some other key features to consider with ASPDNSF, so as to not put you in fear of how scalable it is:

  • FAST SQL option on queries (increased db performance)
  • Built in page and data caching
  • Designed to handle up to 500,000 SKUs (ML/IS versions)

Another thing to consider are some of the impressive sites already running on ASPDNSF. Below are numbers/stats (collected from Compete) for some of the sites listed on ASPDNSF’s gallery:

  • Crocs.com – 250,000 visitors per month
  • InPhonic.com – 4M visitors per month
  • ReStockIt.com – 150,000 visitors per month

That’s about it! Comments are welcome, and keep checking back for more ASPDNSF and Commerce Server articles.

10
Jun
07

Solutions Customization and Integration – Part II

Update on this project… So far I am in the stages of selecting an Learning Management System (LMS) that is SCORM compliant and offers tools to manage courses, students, learning material and deliver it in a lightweight format. One of the biggest hurdles is selecting one that has an open API/SDK to interface with Flash Streaming Video and even synchronize content with the video – e.g. time coding frames etc.

As for the social networking and commerce tools, I have selected Community Server 2007 Enterprise and AspDotNetStorefront ML. Integrating both solutions should not be too complicated since they are both .NET 2.0 solutions, offer the entire source code with the license, and operate on IIS, SQL Server 2005, ASP.NET etc.

The biggest challenge with integrating these pieces is architecting a single sign-on model. LDAP and Active Directory are possible options, with the latter more in the headlights since we are working in a 100% Windows environment. ASPDNSF and CS 2007 can integrate fairly easily for the single sign-on, and since both are somewhat independent systems, there should be little effort to get that going.

The LMS solution will be more involved since we have to map data across the community site and LMS site (e.g. learning material, class forums and discussion groups, blogs on courses etc.). Table structures are fairly open and scalable, however we will very likely use SQL Server Replication and SSIS packages to handle the back-end integration and sharing of data across systems. On the user-facing site, meshing everything together will involve a blend of ASP.NET Master Pages (what CS 2007 uses), and XML/XSLT packages (what ASPDNSF uses), and possibly a customized Master Page and .ascx control architecture for the LMS solution.

The physical architecture that has been mapped out so far includes:

> 2 load balanced Windows 2003 Web servers – 200GB HD, 4GB RAM, 32-bit dual-core, RAID config.
> Single 64-bit SQL Server, 8GB RAM, 200GB HD.
> 1TB SAN (EMC or DELL) – blogs, photos and a subset of videos.
> Fibre Channel across all machines
> Load balancer, firewall etc.
> Content Delivery Network for bulk of Flash videos and larger photos

More details on these integrations in my next post…




Share This


Bookmark and Share

About Me

Technical architect and project manager, with more than 10 years of progressive experience in ERP, e-Commerce, Internet/Web platforms and solution/enterprise architecture. Trained in Microsoft/SAP business products and platforms, with formal educational background in Computer Science, Software Architecture/Engineering and Relational Databases.

View Patrick Rayes's profile on LinkedIn

Blog Stats

  • 15,940 hits

del.icio.us

Flickr Photos

dyson airblade

winter road

closing time

More Photos

Twitter

Calendar

June 2007
M T W T F S S
« May   Aug »
 123
45678910
11121314151617
18192021222324
252627282930