[Paper] A Methodology to Develop Service Oriented Evolutionary Algorithms

Paper about our methodology for service oriented EAs

OSGiLiath Evolutionary Framework

Our paper A Methodology to Develop Service Oriented Evolutionary Algorithms has been published in the proceedings of the 8th International Symposium on Intelligent Distributed Computing – IDC’2014. This paper is a resume of the SOA-EA methodology, one of the chapters of my thesis (available here). The presentation, made by JJ Merelo, is quite cool:


The abstract:

This paper proposes a methodology to design and implement Evolutionary Algorithms using the Service Oriented Architecture paradigm. This paradigm allows to deal with some of the shortcomings in the Evolutionary Algorithms area, facilitating the development, integration, standardization of services that conform a evolutionary algorithm, and, besides, the dynamic alteration of those elements in runtime.
A four-step methodology to design services for Evolutionary Algorithms is presented: identification, specification, implementation and deployment. Also, as an example of application of this methodology, an adaptive algorithm is developed.

You can download the paper draft from…

View original post 15 more words


DECIE2011: Distributed Evolutionary Computation using REST

This paper analises distributed evolutionary computation based on the Representational State Transfer (REST) protocol, which overlays a farming model on evolutionary computation.
An approach to evolutionary distributed optimisation of multilayer perceptrons (MLP) using REST and language Perl has been done. In these experiments, a master-slave based evolutionary algorithm (EA) has been implemented, where slave processes evaluate the costly fitness function (training a MLP to solve a classification problem).
Obtained results show that the parallel version of the developed programs obtains similar or better results using much less time than the sequential version, obtaining a good speedup.

DECIE2011: SOAP vs REST: Comparing a master-slave GA implementation

In this paper, a high-level comparison of both SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) is made. These are the two main approaches for interfacing to the web with web services.
Both approaches are different and present some advantages and disadvantages for interfacing to web services: SOAP is conceptually more difficult (has a steeper learning curve) and more ”heavy-weight” than REST, although it lacks of standards support for security.
In order to test their eficiency (in time), two experiments have been performed using both technologies:
a client-server model implementation and a master-slave based genetic algorithm (GA).
The results obtained show clear differences in time between SOAP and REST implementations.
Although both techniques are suitable for developing parallel systems, SOAP is heavier than REST, mainly due to the verbosity of SOAP communications (XML increases the time taken to parse the messages).