Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Architecture design question

Reply
Thread Tools

Architecture design question

 
 
Griff
Guest
Posts: n/a
 
      10-08-2004
Hi

I'm after some advice about the architecture to employ for a web front-end.

First, I'll describe the system. We host several customers' back-office
systems (which are identical) and which are accessed by our customers'
employees by remote connection. Our customers now wish us to host an
eCommerce front-end to their back-office systems on which *their* customers
will place orders.

By and large, the business rules for all our customers will be identical.
So, my thought was to build a single n-tier system to handle this.

The bottom tier is obviously our customers back-office systems.
The next vertical tier would be a data-services tier that knows which
back-office system to query.
The next would be the business tier.
And then we get to the UI.

It's the UI tier that I'm most confused about.

Each of our customers will require a unique look and feel - some may want a
frames solution, another may want a tabular display, some may want the
navigation buttons along the top whilst another will want them down the
side. Yes, I'm sure that I could program this in to a system, but I'm not
sure the best approach to take. Any/all suggestions most welcome.

Also, I don't know yet whether to employ a single web site with virtual
directories for each of our customers or to employ a separate web site for
each customer. (A single web site seems sensible just in terms of
incorporating SSL security). Either way, my guess is that I'd like all
customers sites to use as much common code as possible. Could anyone talk
me through ideal architectures for this?

Alternatively, if anyone has any great book suggestions that will help me in
this venture, I'd be really glad to hear of them.

Many thanks in advance

Griff



 
Reply With Quote
 
 
 
 
Freddy
Guest
Posts: n/a
 
      10-08-2004
You can use a single website, custom user controls and css


"Griff" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> Hi
>
> I'm after some advice about the architecture to employ for a web
> front-end.
>
> First, I'll describe the system. We host several customers' back-office
> systems (which are identical) and which are accessed by our customers'
> employees by remote connection. Our customers now wish us to host an
> eCommerce front-end to their back-office systems on which *their*
> customers
> will place orders.
>
> By and large, the business rules for all our customers will be identical.
> So, my thought was to build a single n-tier system to handle this.
>
> The bottom tier is obviously our customers back-office systems.
> The next vertical tier would be a data-services tier that knows which
> back-office system to query.
> The next would be the business tier.
> And then we get to the UI.
>
> It's the UI tier that I'm most confused about.
>
> Each of our customers will require a unique look and feel - some may want
> a
> frames solution, another may want a tabular display, some may want the
> navigation buttons along the top whilst another will want them down the
> side. Yes, I'm sure that I could program this in to a system, but I'm not
> sure the best approach to take. Any/all suggestions most welcome.
>
> Also, I don't know yet whether to employ a single web site with virtual
> directories for each of our customers or to employ a separate web site for
> each customer. (A single web site seems sensible just in terms of
> incorporating SSL security). Either way, my guess is that I'd like all
> customers sites to use as much common code as possible. Could anyone talk
> me through ideal architectures for this?
>
> Alternatively, if anyone has any great book suggestions that will help me
> in
> this venture, I'd be really glad to hear of them.
>
> Many thanks in advance
>
> Griff
>
>
>



 
Reply With Quote
 
 
 
 
Griff
Guest
Posts: n/a
 
      10-08-2004
Thanks Freddy

Any suggestions for reading matter, particularly w.r.t. custom user controls
and css.

Presumably, there would be one CSS per customer (of ours). And, if our
customers wanted specific fonts/colours then they'd have their own end-user
style sheets?

Thanks

Griff


 
Reply With Quote
 
Freddy
Guest
Posts: n/a
 
      10-08-2004
You can use asp.net Wrox press books as well as refer to msdn. For CSS
Google it and you can find many free tutorials.


"Griff" <(E-Mail Removed)> wrote in message
news:udv$(E-Mail Removed)...
> Thanks Freddy
>
> Any suggestions for reading matter, particularly w.r.t. custom user
> controls
> and css.
>
> Presumably, there would be one CSS per customer (of ours). And, if our
> customers wanted specific fonts/colours then they'd have their own
> end-user
> style sheets?
>
> Thanks
>
> Griff
>
>



 
Reply With Quote
 
clintonG
Guest
Posts: n/a
 
      10-08-2004
ASP.NET 2.0 solves the problem but is not targeted for
commercial release until Q2 2005. Regardless, I suggest
you study its membership and theming capabilities.

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET http://www.velocityreviews.com/forums/(E-Mail Removed)
URL http://www.metromilwaukee.com/clintongallagher/



"Griff" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> Hi
>
> I'm after some advice about the architecture to employ for a web

front-end.
>
> First, I'll describe the system. We host several customers' back-office
> systems (which are identical) and which are accessed by our customers'
> employees by remote connection. Our customers now wish us to host an
> eCommerce front-end to their back-office systems on which *their*

customers
> will place orders.
>
> By and large, the business rules for all our customers will be identical.
> So, my thought was to build a single n-tier system to handle this.
>
> The bottom tier is obviously our customers back-office systems.
> The next vertical tier would be a data-services tier that knows which
> back-office system to query.
> The next would be the business tier.
> And then we get to the UI.
>
> It's the UI tier that I'm most confused about.
>
> Each of our customers will require a unique look and feel - some may want

a
> frames solution, another may want a tabular display, some may want the
> navigation buttons along the top whilst another will want them down the
> side. Yes, I'm sure that I could program this in to a system, but I'm not
> sure the best approach to take. Any/all suggestions most welcome.
>
> Also, I don't know yet whether to employ a single web site with virtual
> directories for each of our customers or to employ a separate web site for
> each customer. (A single web site seems sensible just in terms of
> incorporating SSL security). Either way, my guess is that I'd like all
> customers sites to use as much common code as possible. Could anyone talk
> me through ideal architectures for this?
>
> Alternatively, if anyone has any great book suggestions that will help me

in
> this venture, I'd be really glad to hear of them.
>
> Many thanks in advance
>
> Griff
>
>
>



 
Reply With Quote
 
Colin Young
Guest
Posts: n/a
 
      10-08-2004
In addition to the good suggestions already made, I'd like to add that one
way to reduce complexity in this sort of situation is to limit the options
in changing the site layout. That's actually less restrictive than it sounds
with decent CSS coding skills. As long as all pages have the same components
on them you should be able to use CSS to lay them out almost any way the
customer wants. You don't want to get into providing a frames solution for
some customers and a single page for others. You'll end up with too much
duplicated code.

If you go with the single-site solution, you need a good method to ensure
that the sites don't bleed into each other (e.g. if you are browsing company
A's site, there shouldn't be products or services from company B showing up,
even if they do appear in the style of company A's site). You will also need
a way to distinguish which site the user has requested. Do you want to use
www.hostcompany.com/?custid=A or www.companya.com? Either way, you'll want
to encapsulate all the code to detect which site the user has requested into
one area.

To handle your customers' business rules, if you haven't already done so,
consider using a rules engine to implement them. Inevitably somebody will
need a different rule, and with a good engine you can even let your
customers manage their own rules (if you so desire).

Colin

"Griff" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> Hi
>
> I'm after some advice about the architecture to employ for a web

front-end.
>
> First, I'll describe the system. We host several customers' back-office
> systems (which are identical) and which are accessed by our customers'
> employees by remote connection. Our customers now wish us to host an
> eCommerce front-end to their back-office systems on which *their*

customers
> will place orders.
>
> By and large, the business rules for all our customers will be identical.
> So, my thought was to build a single n-tier system to handle this.
>
> The bottom tier is obviously our customers back-office systems.
> The next vertical tier would be a data-services tier that knows which
> back-office system to query.
> The next would be the business tier.
> And then we get to the UI.
>
> It's the UI tier that I'm most confused about.
>
> Each of our customers will require a unique look and feel - some may want

a
> frames solution, another may want a tabular display, some may want the
> navigation buttons along the top whilst another will want them down the
> side. Yes, I'm sure that I could program this in to a system, but I'm not
> sure the best approach to take. Any/all suggestions most welcome.
>
> Also, I don't know yet whether to employ a single web site with virtual
> directories for each of our customers or to employ a separate web site for
> each customer. (A single web site seems sensible just in terms of
> incorporating SSL security). Either way, my guess is that I'd like all
> customers sites to use as much common code as possible. Could anyone talk
> me through ideal architectures for this?
>
> Alternatively, if anyone has any great book suggestions that will help me

in
> this venture, I'd be really glad to hear of them.
>
> Many thanks in advance
>
> Griff
>
>
>



 
Reply With Quote
 
Adrian Parker
Guest
Posts: n/a
 
      10-12-2004
What I've done is to have generic pages in one area and then seperate
directories for each customer, and in there put some html pages that I open
and read and then output them to the screen. Can't do aspx page that way,
but you can


"Colin Young" <(E-Mail Removed)> wrote in message
news:uR%(E-Mail Removed)...
> In addition to the good suggestions already made, I'd like to add that one
> way to reduce complexity in this sort of situation is to limit the options
> in changing the site layout. That's actually less restrictive than it
> sounds
> with decent CSS coding skills. As long as all pages have the same
> components
> on them you should be able to use CSS to lay them out almost any way the
> customer wants. You don't want to get into providing a frames solution for
> some customers and a single page for others. You'll end up with too much
> duplicated code.
>
> If you go with the single-site solution, you need a good method to ensure
> that the sites don't bleed into each other (e.g. if you are browsing
> company
> A's site, there shouldn't be products or services from company B showing
> up,
> even if they do appear in the style of company A's site). You will also
> need
> a way to distinguish which site the user has requested. Do you want to use
> www.hostcompany.com/?custid=A or www.companya.com? Either way, you'll want
> to encapsulate all the code to detect which site the user has requested
> into
> one area.
>
> To handle your customers' business rules, if you haven't already done so,
> consider using a rules engine to implement them. Inevitably somebody will
> need a different rule, and with a good engine you can even let your
> customers manage their own rules (if you so desire).
>
> Colin
>
> "Griff" <(E-Mail Removed)> wrote in message
> news:%23$(E-Mail Removed)...
>> Hi
>>
>> I'm after some advice about the architecture to employ for a web

> front-end.
>>
>> First, I'll describe the system. We host several customers' back-office
>> systems (which are identical) and which are accessed by our customers'
>> employees by remote connection. Our customers now wish us to host an
>> eCommerce front-end to their back-office systems on which *their*

> customers
>> will place orders.
>>
>> By and large, the business rules for all our customers will be identical.
>> So, my thought was to build a single n-tier system to handle this.
>>
>> The bottom tier is obviously our customers back-office systems.
>> The next vertical tier would be a data-services tier that knows which
>> back-office system to query.
>> The next would be the business tier.
>> And then we get to the UI.
>>
>> It's the UI tier that I'm most confused about.
>>
>> Each of our customers will require a unique look and feel - some may want

> a
>> frames solution, another may want a tabular display, some may want the
>> navigation buttons along the top whilst another will want them down the
>> side. Yes, I'm sure that I could program this in to a system, but I'm
>> not
>> sure the best approach to take. Any/all suggestions most welcome.
>>
>> Also, I don't know yet whether to employ a single web site with virtual
>> directories for each of our customers or to employ a separate web site
>> for
>> each customer. (A single web site seems sensible just in terms of
>> incorporating SSL security). Either way, my guess is that I'd like all
>> customers sites to use as much common code as possible. Could anyone
>> talk
>> me through ideal architectures for this?
>>
>> Alternatively, if anyone has any great book suggestions that will help me

> in
>> this venture, I'd be really glad to hear of them.
>>
>> Many thanks in advance
>>
>> Griff
>>
>>
>>

>
>



 
Reply With Quote
 
Adrian Parker
Guest
Posts: n/a
 
      10-12-2004
What I've done is to have generic pages in one area and then seperate
directories for each customer, and in there put some html pages that I open
and read and then output them to the screen. Can't do aspx page that way,
but you can load specific aspx pages from there.

"Colin Young" <(E-Mail Removed)> wrote in message
news:uR%(E-Mail Removed)...
> In addition to the good suggestions already made, I'd like to add that one
> way to reduce complexity in this sort of situation is to limit the options
> in changing the site layout. That's actually less restrictive than it
> sounds
> with decent CSS coding skills. As long as all pages have the same
> components
> on them you should be able to use CSS to lay them out almost any way the
> customer wants. You don't want to get into providing a frames solution for
> some customers and a single page for others. You'll end up with too much
> duplicated code.
>
> If you go with the single-site solution, you need a good method to ensure
> that the sites don't bleed into each other (e.g. if you are browsing
> company
> A's site, there shouldn't be products or services from company B showing
> up,
> even if they do appear in the style of company A's site). You will also
> need
> a way to distinguish which site the user has requested. Do you want to use
> www.hostcompany.com/?custid=A or www.companya.com? Either way, you'll want
> to encapsulate all the code to detect which site the user has requested
> into
> one area.
>
> To handle your customers' business rules, if you haven't already done so,
> consider using a rules engine to implement them. Inevitably somebody will
> need a different rule, and with a good engine you can even let your
> customers manage their own rules (if you so desire).
>
> Colin
>
> "Griff" <(E-Mail Removed)> wrote in message
> news:%23$(E-Mail Removed)...
>> Hi
>>
>> I'm after some advice about the architecture to employ for a web

> front-end.
>>
>> First, I'll describe the system. We host several customers' back-office
>> systems (which are identical) and which are accessed by our customers'
>> employees by remote connection. Our customers now wish us to host an
>> eCommerce front-end to their back-office systems on which *their*

> customers
>> will place orders.
>>
>> By and large, the business rules for all our customers will be identical.
>> So, my thought was to build a single n-tier system to handle this.
>>
>> The bottom tier is obviously our customers back-office systems.
>> The next vertical tier would be a data-services tier that knows which
>> back-office system to query.
>> The next would be the business tier.
>> And then we get to the UI.
>>
>> It's the UI tier that I'm most confused about.
>>
>> Each of our customers will require a unique look and feel - some may want

> a
>> frames solution, another may want a tabular display, some may want the
>> navigation buttons along the top whilst another will want them down the
>> side. Yes, I'm sure that I could program this in to a system, but I'm
>> not
>> sure the best approach to take. Any/all suggestions most welcome.
>>
>> Also, I don't know yet whether to employ a single web site with virtual
>> directories for each of our customers or to employ a separate web site
>> for
>> each customer. (A single web site seems sensible just in terms of
>> incorporating SSL security). Either way, my guess is that I'd like all
>> customers sites to use as much common code as possible. Could anyone
>> talk
>> me through ideal architectures for this?
>>
>> Alternatively, if anyone has any great book suggestions that will help me

> in
>> this venture, I'd be really glad to hear of them.
>>
>> Many thanks in advance
>>
>> Griff
>>
>>
>>

>
>



 
Reply With Quote
 
Griff
Guest
Posts: n/a
 
      10-12-2004

> To handle your customers' business rules, if you haven't already done so,
> consider using a rules engine to implement them.


Could you define a "rules engine" please...


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
CFP - Journal of Systems Architecture, Embedded Software Design(Elsevier), Special Issue on Hardware/Software Co-Design Juan A. Gomez-Pulido VHDL 0 08-24-2009 02:11 PM
2nd. CFP - Journal of Systems Architecture - Embedded Software Design(Elsevier) - Special Issue on HARDWARE/SOFTWARE CO-DESIGN Juan A. Gomez-Pulido VHDL 0 05-24-2009 03:14 PM
collocated architecture versus distributed architecture apngss@yahoo.com Java 3 09-29-2005 07:44 AM
how can I use a signal defined in one Architecture to another Architecture Muhammad Khan VHDL 4 07-10-2003 06:14 PM



Advertisments