SOAP vs REST: Comparing a  master-slave GA implementation P. A. Castillo, J. L. Bernier, M. G. Arenas,  J. J. Merelo , P. ...
Web services are the core of Web 2.0 SOAP REST XML-RPC SOA BPEL
Why any of them? <ul><li>Web services integrate many business processes.
Evolutionary algorithms can be a part of a  wider service-oriented architecture
Optimization  can be offered also  as a service </li></ul>
Why informal? <ul><li>Web services have been adopted by many communities (e.g. Bioinformatics)
Single-program or parallel implementations are still standard.
A few papers using SOAP.
Very few compare it with other WS. </li></ul>
SOAP and REST <ul><li>Simple object access architecture
OASIS standard
Object oriented access for remote objects
Widely implementened </li></ul><ul><li>Representational State Protocol
Interaction style for web services
Access remote content using HTTP protocol. </li></ul>
Upcoming SlideShare
Loading in …5
×

SOAP vs REST: Comparing a master-slave GA implementation

1,423 views

Published on

Presentation for paper at IWDECIE: http://arxiv.org/abs/1106.0118

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

  • Be the first to like this

No Downloads
Views
Total views
1,423
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Image from http://www.flickr.com/photos/justinjensen/5612967697/
  • SOAP vs REST: Comparing a master-slave GA implementation

    1. 1. SOAP vs REST: Comparing a master-slave GA implementation P. A. Castillo, J. L. Bernier, M. G. Arenas, J. J. Merelo , P. García-Sánchez GeNeura Group University of Granada (Spain) Http://geneura.wordpress.com Http://twitter.com/geneura
    2. 2. Web services are the core of Web 2.0 SOAP REST XML-RPC SOA BPEL
    3. 3. Why any of them? <ul><li>Web services integrate many business processes.
    4. 4. Evolutionary algorithms can be a part of a wider service-oriented architecture
    5. 5. Optimization can be offered also as a service </li></ul>
    6. 6. Why informal? <ul><li>Web services have been adopted by many communities (e.g. Bioinformatics)
    7. 7. Single-program or parallel implementations are still standard.
    8. 8. A few papers using SOAP.
    9. 9. Very few compare it with other WS. </li></ul>
    10. 10. SOAP and REST <ul><li>Simple object access architecture
    11. 11. OASIS standard
    12. 12. Object oriented access for remote objects
    13. 13. Widely implementened </li></ul><ul><li>Representational State Protocol
    14. 14. Interaction style for web services
    15. 15. Access remote content using HTTP protocol. </li></ul>
    16. 16. SOAP Strengths <ul><li>Handle distributed computing environments
    17. 17. Built-in error handling
    18. 18. Extensibility
    19. 19. Language, platform, and transport agnostic
    20. 20. Prevailing standard for web services
    21. 21. Support from other standards (WSDL, WS-*) </li></ul>Weaknesses <ul><li>Verbose
    22. 22. Harder to develop, requires tools
    23. 23. Conceptually more difficult, more heavy-weight than REST </li></ul>
    24. 24. REST Strengths <ul><li>Language and platform agnostic
    25. 25. Much simpler to develop than SOAP
    26. 26. Small learning curve, less reliance on tools
    27. 27. Concise, no need for additional messaging layer
    28. 28. Closer in design and philosophy to the Web </li></ul>Weaknesses <ul><li>Assumes a point-to-point communication model
    29. 29. Not usable for distributed computing environment
    30. 30. Lack of standards support for security, etc.
    31. 31. Tied to the HTTP transport model </li></ul>
    32. 32. Which one is better for a master/slave implementation of an evolutionary algorithm?
    33. 33. How does REST work?
    34. 34. Experiments <ul><li>Using Ubuntu
    35. 35. Servers/clients written in Perl </li><ul><li>SOAP::Lite
    36. 36. PerlDancer framework for REST </li></ul><li>Evolutionary Algorithm uses perl AE library Algorithm::Evolutionary </li></ul>
    37. 37. Raw performance <ul><li>Sending and receiving text strings </li></ul>
    38. 38. Tide function
    39. 39. Master/Slave EA implementation
    40. 40. REST rules! Different implementations do not have an effect on the evolutionary algorithm, but SOAP can be 50% slower
    41. 41. Any question? Thanks.

    ×