Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For the sake of good practice, I would break up the API into separate interfaces so you have the option of splitting them into separate implementations in the future. You can still have just one service class implement all of the interfaces, like this:</p> <pre><code>public class RestService : ICustomer, IProducts, IOrders </code></pre> <p>However, it sounds as if you'd probably want to make them separate implementations anyway.</p> <p>In terms of concurrency settings, ask yourself what resources need to be used on each call. If your service class's constructor can be written without any lengthy startup, then use PerCall. If you need to initialize expensive resources, then I'd recommend InstanceContextMode.Single with ConcurrencytMode.Multiple and make sure you write thread-safe code. Eg: make sure you lock() on any class properties or other shared resources before you use them.</p> <p>Database connections would <em>not</em> count as "expensive to initialize", though, because ADO will do connection pooling for you and eliminate that overhead.</p> <p>Your throttling settings will be revealed by testing, as Ladislav mentions. You'd want to stress-test your service and use the results to get an idea of how many machines you'd need to service your anticipated load. Then you'll need a dedicated load balancer to route requests as either round-robin, or something that checks the health of each server. Load balancers can be set up to GET a "systemhealth.asp" page and check the results. If you return an "OK" then that machine stays in the pool, or can be temporarily removed from the pool if it times out or returns any other status.</p> <p>Your binding would need to be WebHTTPBinding for REST. BasicHTTPBinding is meant for SOAP interfaces and doesn't support [WebGet], for example.</p> <p>If it doesn't have to be a REST service, then you can get a bit more performance by using NetTcpBinding. </p>
    singulars
    1. This table or related slice is empty.
    1. POWCF Optimal performance settings
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris Wenham
    1. USChris Wenham
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWCF Optimal performance settings
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COHi thanks for taking time out to respond. Where would i put the method which relates to the interfaces, would they go into the "RestService" class. For instance, getCustomersByID will that go into a customer class?
      singulars
      1. PO
      1. USpmillio
    2. COYes, if you wanted to break each responsibility (customers, products, orders) into separate classes you'd just define an interface for each of them first (ICustomer, IProducts, IOrders), and then create three classes that implement each--with their respective methods. The only good reason for combining all three into a single class would be if they had few methods, shared some kind of state, and you wanted to keep it simple. If they have lots of methods then it's definitely a good idea to break them up.
      singulars
      1. PO
      1. USChris Wenham
    3. COThanks once again, ok after i create and interface and class for each seperate one, how do i go about calling them from just one service, i hope i am making sense.
      singulars
      1. PO
      1. USpmillio
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload