Re: Structuring of large application

From: Brandon Potter (msnews_at_brandonpotter_nospam.com)
Date: 01/05/05 

Date: Wed, 5 Jan 2005 06:43:17 -0500

Have you thought about possibly writing the business logic & data layer in
one application as a web service, and writing the UI in your regular web
app?

Sometimes people will assign a GUID to a user at the start of a session and
keep their current session's login information in a database, and simply
pass the GUID along to another application when they "jump over the wall",
so to speak. Again your central login database could be another web services
app.

Brandon

"Damien" <Damien_The_Unbeliever@hotmail.com> wrote in message
news:1104919015.363665.323740@z14g2000cwz.googlegroups.com...
> Hey guys,
>
> I'm currently developing a reasonably sized application, which is
> expected to grow in the future.
>
> At the centre is the User login facility - everyone using the site must
> log in. Thereafter, various different services may be available to the
> user, dependant on how they are set up - there are currently two
> services available:
>
> Creditor Services
> User Management
>
> Because there are a lot of tie-ups between the services, and a lot of
> shared data, all of the data resides in a single database (but
> service-specific information is stored under separate schemas). A
> single data-access layer provides access to the database, and the
> services share session management facilities.
>
> At present, because of the large number of tie-ups between the
> services, the system is structured as a single monolythic web
> application.
>
> I tried to break it down a bit by placing service specific pages within
> subdirectories. However, ASP.NET couldn't seem to cope with this, and
> couldn't manage to create/find the code-behind associated with these
> pages.
>
> Even if I split the services out into completely separate web
> applications, I still want them to be able to share session information
> and there are a fair number of common pages/common code between them.
>
> How would you guys suggest I go about restructuring, before the next
> service comes along and makes the job even harder?
>
> Ideally I would like the common login facility (and initial service
> selection) pages to reside at the root of the site, and then for each
> service to reside within a (virtual) directory below that.
> Any pointers?
>

Relevant Pages

  • Re: Bit flipping .. will this work in VB6?
    ... such as you or another programmer on the project writing ... reporting some odd behavior can send me the file they are working on, ... in the database even though they had 190gig free on the hdd. ... If you're writing a financial app though.... ...
    (microsoft.public.vb.general.discussion)
  • Re: Can I programmatically IMPORT data from XML into Access?
    ... First, I know Access 2000 didn't have the ImportXML method, but I'm not sure ... Given the overhead involved in COM Interop and Automation, ... How many records can I write to a database in 5 seconds? ... you can provide more information about how you're writing to the database ...
    (microsoft.public.access.externaldata)
  • Re: Can I programmatically IMPORT data from XML into Access?
    ... >From your test results I realize that my result is quite expected (writing ... > Given the overhead involved in COM Interop and Automation, ... How many records can I write to a database in 5 seconds? ... > performance advantages from going the automation route. ...
    (microsoft.public.access.externaldata)
  • Re: general archetecture questions.
    ... > first app i'm writing will be using XML as a database of sorts, using> dataset and dataview and wrapped up in a set of classes. ... in the past i used> ".getinstance" in java to get a single instance of a class contained in a application variable to ensure i dont have 3-4> different instances hitting the database and worse now writing 3-4 different> xml files. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SQL2000/ASP.Net performance question
    ... functionality is not currently supported by the existing data layer however ... >> from the web form will generate a record in a single table in the ... >> Given my current data layer I'm connecting to the database for each ...
    (microsoft.public.sqlserver.programming)
Quantcast