Pierre,

 

I'm getting stuck into the code to get a better understanding of how it all
hangs together. In the market we're addressing there is a degree of paranoia
about competitors being able to see one's prices, so it is not unusual to
hide the entire web store behind a login and use a customer-specific URL
even to see the catalog. These are mostly B2B players so it's not [quite] as
insane as it first sounds! Actually each tenant may well have multiple
sites, i.e. they have separate catalogs, style sheets, etc. for many of
their customer companies.

 

I am extremely impressed with OfBiz.

 

Regards,

 

Gareth.

 

 

From: Pierre Smits-3 [via OFBiz]
[mailto:[email protected]] 
Sent: 11 October 2011 08:48
To: gobrien
Subject: Re: Multi-tenant ecommerce

 

Hi Gareth, 

IMO, I would not like to see that a (potential) customer would be required 
to enter the tenant ID, as this would surely deminish user satisfaction. And

on the other hand passing the tenant ID in a url would also not be 
preferable regarding security issues. 

I can imagine that the webstore of each tenant would be requiring specific 
style sheets and componant layouts, so that would lead to having to maintain

several dedicated instances of the ecommerce application and associated 
themes. Plus, if you are indeed talking about so many tenants and eStores 
times several hundreds of users (viewers, clients and backend users) you 
would have to have some high availability c.q. failover solution in place. 

Today the front end (the ecommerce) component relies heavily on several 
backend components, where handling of tenant delegation is already in place.

So the ecommerce application should only contain the bear necessities to 
deliver the tenant dedicated eStore. 

With regards, 

Pierre Smits 

2011/10/10 gobrien <[hidden email]> 


> Thanks for the reply Pierre. 
> 
> So the current design is that each web store is a separate web application

> attached to a particular tenantId? 
> 
> I was thinking of a single web application that is connected to the 
> appropriate database in similar manner to the way the back-end works. The 
> tenantId would be passed either in the URL or tenantId in the login widget

> as currently in the back end. 
> 
> The majority of my experience has been in MS .NET, IIS, etc. As a result I

> might be over thinking this ... 
> 
> I'm thinking that the management overhead of say 500 web applications on 
> the 
> disk would become tedious. More importantly, I'm wondering if/how much 
> performance penalty would there be to running multiple web applications 
> rather than one web application for all sites. Is this a valid concern
with 
> Tomcat? 
> 
> Do you have a gut feel for whether reducing such performance concern would

> be worth the dev effort? 
> 
> Thanks, 
> 
> Gareth. 
> 
> -- 
> View this message in context: 
>
http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3889648.h
tml
> Sent from the OFBiz - Dev mailing list archive at Nabble.com. 
> 

 

  _____  

If you reply to this email, your message will be added to the discussion
below:

http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3893111.h
tml 

To unsubscribe from Multi-tenant ecommerce, click here
<http://ofbiz.135035.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscrib
e_by_code&node=3888115&code=Z29icmllbkB5dXBvbi5jb218Mzg4ODExNXwtNjc4ODkwNTk2
> . 



--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3893139.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Reply via email to