Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Create an interface for the service layer, internally all your code can work with that. Then make a class that uses that interface and calls the third party api methods and as the api facade.</p> <p>i.e.</p> <pre><code>interface IAPIEndpoint { MyDomainDataEntity getData(); } class MyAPIEndpoint : IAPIEndpoint { public MyDomainDataEntity getData() { MyDomainDataEntity dataEntity = new MyDomainDataEntity(); // Call the third party api and fill it return dataEntity; } } </code></pre> <p>It is always a good idea to interface out third party apis so you don't get their funk invading your app domain, and you can swap out as needed. You could make another class implementation that uses a different service entirely.</p> <p>To use it in code you just call </p> <pre><code>IAPIEndpoint endpoint = new MyAPIEndpoint(); // or get it specific to the lang you are using. </code></pre> <p>Making your stuff based on interfaces when it spans multiple implementations is the way to go. It works great for TDD as well so you can just swap out the interface to a local test one that can inspect your domain code entirely separate from the third party api.</p>
    singulars
    1. This table or related slice is empty.
    1. PONeed help improving a tightly coupled design
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRyan Christensen
    1. USRyan Christensen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONeed help improving a tightly coupled design
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Ryan, I think that makes sense. Let me ask a question to make sure I understand: I can use this approach and create the interface - in one impl I can call the third party api, in another impl I can call a test impl of the api so I can test in isolation. Is that correct? My concern is how I'm going to handle the methods in the API object when I have to call them (mostly set/get but there are some methods).
      singulars
      1. PO
      1. USJasonH
    2. COYeh finding common ground is always tricky. Yes the interface describes what you app will use consistently across all implementations (classes using the interface or impl in java world). I tend to put only the common methods that are 'genericized' into the main interface. Then any specific api methods that are used by these methods in an implementation can do specific methods for the implementation. For instance here we have a matchup server and we call an interface for FindMatch(), StartMatch(), CloseMatch() etc. Those are in the interface. Then in a Gamecenter...
      singulars
      1. PO
      1. USRyan Christensen
    3. COimplementation of that class we use the GameCenter calls to get a match, start a match, close a match and have many other methods that those calls use specific to GameCenter as private methods. Then we can easily swap with a Test implementation that locally runs and also another matchup server that is self-hosted. So our three third party or unique uses are all commonized by the interface with generic calls. HTH Interfaces are also very common in web service server/client setups where all the code might not be on the client and only the interface and container classes need to be present.
      singulars
      1. PO
      1. USRyan Christensen
 

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