Large scale deployment

Poster

Content

pjr

nk4um Moderator

Posts: 756

May 28, 2007 09:48Large scale deployments

Hi Schikb,

Welcome to the NetKernel community. Your proposed architecture is definitely well proven - one of our oldest customers has been in production for several years using NetKernel behind a very large scale web property. Unfortunately for commercial reasons we''re not able to publicly say which site this is.

Our customers page on the 1060research.com site points to some other similar examples.

I completely understand the need to establish confidence in infrastructural software. I''m very pleased to say that NetKernel has been around for nearly 5 years now and is the basis of many large scale commercial systems.

Cheers,

Peter

schickb

nk4um User

Posts: 1

<div>I am investigating various approaches for developing a web-app that (if successful) will need to scale to millions of page hits per day and up.<br/><br/>Has NetKernel been used in such an environment? I understand that the concepts upon which it is based are specifically intended to enable scaling. But I''m wondering if NetKernel (as an implementation of those concepts) has been pounded on enough to verify that it has the durability and internal performance to handle such loads. <br/><br/>I''m imagining that NetKernel would be on back-end systems, but I''m also wondering if anyone has tried to use it on scaled-out front-end systems. My rough idea is something like this:<br/><br/><table align="center" border="0" cellpadding="3" cellspacing="1" width="90%"><tr><td><div class="forum-code"><pre>back-end           cache       front-end<br/>--------           -----       ---------<br/><br/>Netkern-1-----                 -----httpd-1<br/>             |                 |<br/>Netkern-2----------Squid------------httpd-2<br/>             |                 |<br/>NetKern-N-----                 -----httpd-N</pre></div></td></tr></table><br/>In practice there would be many more front-ends than back-ends. The primary idea behind squid is to consolidate caches, but it also has many nice cache specific features. The back-end NetKern servers would not all be identical (although some might be load balanced clones) and sit atop various resources like RDBMS, static files, external data, etc.<br/><br/>Anyway, I''ve been pondering this all day and wanted some feedback since it''s rather different from what I''ve done previously.<br/><br/>Thanks,<br/>-Brad</div>

May 28, 2007 07:40Large scale deployment

I am investigating various approaches for developing a web-app that (if successful) will need to scale to millions of page hits per day and up.

Has NetKernel been used in such an environment? I understand that the concepts upon which it is based are specifically intended to enable scaling. But I''m wondering if NetKernel (as an implementation of those concepts) has been pounded on enough to verify that it has the durability and internal performance to handle such loads.

I''m imagining that NetKernel would be on back-end systems, but I''m also wondering if anyone has tried to use it on scaled-out front-end systems. My rough idea is something like this:

back-end           cache       front-end
--------           -----       ---------

Netkern-1-----                 -----httpd-1
             |                 |
Netkern-2----------Squid------------httpd-2
             |                 |
NetKern-N-----                 -----httpd-N

In practice there would be many more front-ends than back-ends. The primary idea behind squid is to consolidate caches, but it also has many nice cache specific features. The back-end NetKern servers would not all be identical (although some might be load balanced clones) and sit atop various resources like RDBMS, static files, external data, etc.

Anyway, I''ve been pondering this all day and wanted some feedback since it''s rather different from what I''ve done previously.

Thanks,
-Brad