Web Service

605 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
605
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web Service

  1. 1. Web service
  2. 2. Context
  3. 3. Apakah ini web service?
  4. 4. Perbedaan
  5. 5. Web yg ditambah service
  6. 6. Komponen vs. service <ul><li>reusable </li></ul><ul><li>To be used a component must: </li></ul><ul><ul><li>be packaged to be deployed as </li></ul></ul><ul><ul><li>part of some larger application </li></ul></ul><ul><ul><li>system </li></ul></ul><ul><ul><li>fit with the existing framework </li></ul></ul><ul><ul><li>used to develop the system </li></ul></ul><ul><li>Components can be sold. </li></ul><ul><ul><li>Component developers charge on a per-deployment basis: </li></ul></ul><ul><li>whenever a new client downloads the component. </li></ul><ul><li>There are many component frameworks available for building distributed systems (e.g., J2EE, DCOM, .NET, CORBA). </li></ul><ul><li>The problem is: they are not compatible. </li></ul><ul><li>Web services are reusable too. </li></ul><ul><li>To be used a service must: </li></ul><ul><ul><li>be published on the Web </li></ul></ul><ul><ul><li>advertise its description and location to potential clients across the Web so that they can access it using standard protocols </li></ul></ul><ul><li>Web Services can be sold too. </li></ul><ul><ul><li>Service providers can charge on a per-call basis: each time an existing client interacts with a service by exchanging a new message. </li></ul></ul><ul><li>Web services can be composed into larger systems and (of course) can be found on the Web. </li></ul><ul><li>Unlike components, Web services do not have to be downloaded and deployed in order to be used by clients. </li></ul>
  7. 7. Komponen interoperability
  8. 8. Web service interoperability
  9. 9. Standard interoperability
  10. 10. Standard web service <ul><li>Standard diperlukan karena banyaknya pilihan </li></ul><ul><li>Web service juga memiliki banyak standard (standard baru, sudah hilang, yg masih terus) </li></ul><ul><li>Tanpa standard, interoperability tidak kan terjadi. </li></ul><ul><li>Perlu waktu agar standard diterima secara luas oleh industri. Karena spesifikasi yg diawali dg “WS” bukan jaminan interoperability ada. </li></ul><ul><li>Badan standard WS: </li></ul><ul><ul><li>W3C (World Wide Web Consortium) </li></ul></ul><ul><ul><li>OASIS (Organization for the Advancement of Structured Information Standards) </li></ul></ul><ul><ul><li>WS-I (Web Services Interoperability Organization) </li></ul></ul><ul><ul><li>GGF (Global Grid Forum) </li></ul></ul>
  11. 11. WS standard
  12. 12. Keterbatasan middleware <ul><li>Web service ditujukan untuk mengatasi beberaoa keterbatasan middleware </li></ul><ul><li>Non standard interface </li></ul><ul><ul><li>Sangat mahal untuk membangun sistem tersebar pada berbagai macam platform middleware </li></ul></ul><ul><li>Lack of trust </li></ul><ul><ul><li>Trust domain yang berbeda sangat susah </li></ul></ul><ul><li>Centralized </li></ul><ul><ul><li>Tidak cocok untu B2B </li></ul></ul><ul><li>RPC vs. Messaging </li></ul><ul><ul><li>Interkasi lambat dan asinkron </li></ul></ul>
  13. 17. WS dan Middleware <ul><li>Web service bisa dianggap evolusi dari middleware secara alamiah </li></ul><ul><li>WS standard memungkinkan interoperability antar middleware </li></ul><ul><li>Proses integrasi lebih mudah </li></ul><ul><li>B2B integrasi dimungkinkan (SOAP bisa lewat firewall) </li></ul>
  14. 18. Arsitektur <ul><li>Interpretasi yg umum adalah dari IBM. </li></ul><ul><li>Ada 3 elemen: </li></ul><ul><ul><li>Service requester </li></ul></ul><ul><ul><li>Service provider </li></ul></ul><ul><ul><li>Service regitry </li></ul></ul>
  15. 19. WS standard <ul><li>The Web service architecture proposed by IBM is based on two key concepts: </li></ul><ul><ul><li>architecture of existing synchronous middleware platforms </li></ul></ul><ul><ul><li>current specifications of SOAP, UDDI and WSDL </li></ul></ul><ul><li>The architecture has a remarkable client/server flavor </li></ul><ul><li>It reflects only what can be done with </li></ul><ul><ul><li>SOAP (Simple Object Access Protocol) </li></ul></ul><ul><ul><li>UDDI (Universal Description and Discovery Protocol) </li></ul></ul><ul><ul><li>WSDL (Web Services Description Language) </li></ul></ul>
  16. 20. Service bus <ul><li>Service broker </li></ul>

×