1 / 8

e W EEK

e W EEK. SOA: Future-Tex? The service-oriented prospects for a future-proof infrastructure. Peter Coffee Technology Editor, eWEEK. Web 1.0: www = “ w hat w as w rong”. HTML was supposed to be content notation Hijacked to become a page description language

tale
Download Presentation

e W EEK

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eWEEK

  2. SOA: Future-Tex?The service-oriented prospects for a future-proof infrastructure Peter Coffee Technology Editor, eWEEK

  3. Web 1.0: www = “what was wrong” • HTML was supposed to be content notation • Hijacked to become a page description language • Too difficult to render content on diverse devices • Too many times to the well: constant reloads • Embedded code is crude and fragile • Scripting languages do too little and too much • Inadequate database capabilities • Too little control of client-side privileges • Reuse is by copying, not by inheritance

  4. Why Web Services are Right • Keep code under your control • Code should act on data close at hand • Client-side code uses little of what it retrieves • Code downloads leak intellectual property • Server-side code adds value, aids efficiency • Clarify interface definitions • Put business function implementation with owner • Enable incremental improvement • Create partner opportunities • Service chains • Custom data interfaces

  5. How to do SOA Wrong • Let services grow out of applications • Create multiple instances of services bus……instead of defining one SOA environment • Let service creation run wild……instead of defining governable process • Make it easier to reinvent than reuse……instead of stressing discoverability & security • Confuse modularity with reusability • Jigsaw puzzle pieces are modules……but they only fit together one way • “ABOS” (A Bunch Of Services”) is not SOA

  6. No Unmixed Blessings • Service architecture entails remote trust • Authentication only says whom you can sue • Privilege control is crucial • IPv6 offers leverage: DoD deadline is 2008 • Every line of code can’t be a security risk • Put securability into the stack: do it right just once

  7. No Unmixed Blessings • Self-disclosing data formats use bandwidth • Next-generation networks require XML awareness • Think about audit and compliance in context of future scalability

  8. eWEEK

More Related