Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've learnt fairly quickly to shy away from the term "ESB" as itis very overloaded and means different things to different people (and at times different things to the same person :-))</p> <p>The key thing, naturally, is to ask yourself what it is you actually require.</p> <p>Wrapping your database(s) as a service is likely to be a wise choice, especially if you have multiple client for this data; you will have to spend a good amount of time thinking about your contracts and scoping, but agile can greatly help here. </p> <p>The question is now how do these service get called, and I think you need to weigh the likelihood of the clients and services change and how your system is going to evolve. </p> <p>A service bus helps masking the services from their client (which can be other services) and this "masking" can relayte to location, protocol, formats, codes, etc. some forms of a service bus also maintain the itinerary (what needs to be called, and when) but I generally dislike the idea. </p> <p>so - the question you need to ask yourself first, I think, is what do you require to start with and how much up front investment you are wishing to make (and can justify)</p> <p>For example, if initially you are happy with a more point-to-point approach, your clients can call the service directly; at a later stage, as the service evolves, you can introduce the "middle man" to broker the request and response (yes - you can call it ESB if you like).</p> <p>Alternatively you can start with a basic "middle man", so that the clients never call the service directly, but have just the features you need to begin with and expand it's capabilities as requirements form; it may well start as being a simple forwarding machine.</p> <p>Ideally you would build on top of a product that has many capabilities built in; BizTalk Server is a good matchif you're on MS stack (but has it's learning curve)</p> <p>so - apologise if this is not a very concrete answer - but I guess my main point is that "ESB"does not have to be an overkill, it simply comes down to what you wish to have at day one, and agile (and SOA) definitely helps by allowing you to gradually evolve rather than anything big-bang like.</p> <p>(if anything above is complete nonsense or just a bit unclear it's due to lack of sleep with a new born in the house! apologies :-) )</p>
    singulars
    1. This table or related slice is empty.
    1. POAgile Development and ESBs
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USYossi Dahan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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