Results 1 to 2 of 2
  1. #1
    MatuX is offline Member
    Join Date
    Dec 2008
    Rep Power

    Post Client/Server/Admin, architecture discussion

    Hello everyone,

    Up to now I have built quite a couple of years of experience programming mostly Videogames and Mobile Apps, and right now I'm trying to move to the "Enterprise World" to create more sophisticated applications.

    I'm learning my ways into DBs (currently using MySQL), JDBC, Hibernate, Visual Web apps, Swing, etc.

    At this very moment, I'm trying to come up with a good Client/Server architecture that would allow me to:

    + Have several Clients requesting and storing information on an external DB.
    + Have some way of storing statistical data on the same or another DB given the information flow and also a way of sending information to the existing Clients such as advertising or whatever.
    + And finally, an Administration Application that will allow me to edit the DB, users, etc.
    + Security is an important issue.

    The requirements are a bit more complex but I think that explanation will suffice.
    Now, I came up with this rather simple idea:

    Have several Clients requesting and storing information on an external DB.
    A Server processing these Client requests mostly by storing and sending DB data.
    The Server would also store statistical data on the DB and eventually send update information to the Clients with advertising or whatever.
    An Administration Application that will allow me to edit the DB.

    * Have a MySQL DB running at all times on a Datacenter PC.
    * The Clients won't connect to the DB directly, instead, they would connect to a Server that is a mediator between the Client and the DB, process all the Client requests, query the DB and send the info back to the Client.
    * The Clients need also to store info on the DB, this would be done via the mediator Server as well.
    * This Server would also store statistical data given the Client request flow and usage.
    * The Server would also send advertising to the Client.
    * Finally, a Visual Web admin app would allow administrator to view and edit the DB directly.

    Is this logical? Does it makes any sense? Is it idiotic? Will this be enough? This is the first I'm trying to figure out this kind of architecture and I don't know if I have the correct mind set.

    Any ideas and considerations would be greatly appreciated.

    Thank you in advance!
    Last edited by MatuX; 12-19-2008 at 08:04 PM. Reason: clarification

  2. #2
    racerxadam is offline Member
    Join Date
    Jul 2008
    Rep Power


    This sounds like your average web app. You have a database server that hosts the database and a webapp server that hosts the application. Users connect to the application through a web browser and can execute the application's functionality through different web pages. Changes are then persisted to the database from the application/appserver.

Similar Threads

  1. client-server app
    By shwein in forum Networking
    Replies: 3
    Last Post: 10-14-2008, 05:20 PM
  2. Replies: 1
    Last Post: 10-05-2008, 03:12 PM
  3. client/server palindrom
    By Rgfirefly24 in forum New To Java
    Replies: 0
    Last Post: 04-28-2008, 02:19 AM
  4. Identify Client in Socket Client Server Application
    By masadjie in forum Networking
    Replies: 1
    Last Post: 12-20-2007, 10:18 AM
  5. Java SQL Admin Tool 2.4.2
    By JavaBean in forum Java Software
    Replies: 0
    Last Post: 11-12-2007, 07:05 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts