Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Design and Architecture
  4. Design of WCF

Design of WCF

Scheduled Pinned Locked Moved Design and Architecture
csharpcssdatabasewcfdesign
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mycroft Holmes
    wrote on last edited by
    #1

    I'm interested to find out if it is better to have multiple (8), small services within a solution or to have less but larger services. Our service currently has around 40 model/dal classes (each model class has a dal class), this represents the bulk of the solution but I can see it growing by another 50% before we are done. I'm debating breaking it into smaller services although there is not logical segregation of the database, it would be breaking it to redusce the size only. Is there a significant impact on the server to run multiple services. Each client will need all the services b/c of the homogeneous nature of the data.

    Never underestimate the power of human stupidity RAH

    J 1 Reply Last reply
    0
    • M Mycroft Holmes

      I'm interested to find out if it is better to have multiple (8), small services within a solution or to have less but larger services. Our service currently has around 40 model/dal classes (each model class has a dal class), this represents the bulk of the solution but I can see it growing by another 50% before we are done. I'm debating breaking it into smaller services although there is not logical segregation of the database, it would be breaking it to redusce the size only. Is there a significant impact on the server to run multiple services. Each client will need all the services b/c of the homogeneous nature of the data.

      Never underestimate the power of human stupidity RAH

      J Offline
      J Offline
      JV9999
      wrote on last edited by
      #2

      One entry/exit point for your service is better, but then I would dispatch the logic behind it in several classes with each their own logic/domain etc.. So basically a bit of both :)

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups