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

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. Web services are the core of Web 2.0 SOAP REST XML-RPC SOA BPEL

4. Evolutionary algorithms can be a part of a wider service-oriented architecture

5. Optimization can be offered also as a service

7. Single-program or parallel implementations are still standard.

8. A few papers using SOAP.

9. Very few compare it with other WS.

11. OASIS standard

12. Object oriented access for remote objects

14. Interaction style for web services

15. Access remote content using HTTP protocol.

17. Built-in error handling

18. Extensibility

19. Language, platform, and transport agnostic

20. Prevailing standard for web services

22. Harder to develop, requires tools

23. Conceptually more difficult, more heavy-weight than REST

25. Much simpler to develop than SOAP

26. Small learning curve, less reliance on tools

27. Concise, no need for additional messaging layer

29. Not usable for distributed computing environment

30. Lack of standards support for security, etc.

31. Tied to the HTTP transport model

32. Which one is better for a master/slave implementation of an evolutionary algorithm?

33. How does REST work?

38. Tide function

39. Master/Slave EA implementation

40. REST rules! Different implementations do not have an effect on the evolutionary algorithm, but SOAP can be 50% slower

41. Any question? Thanks.