Dear all, as you may know in the SmartSDK project we are working on reference FIWARE data and iot architectures based on cloud patterns. in the work we do it is crucial to analyse the architecture of the single enabler and understand how to apply cloud patterns to it (e.g. high availability, scalability, …) the basic starting point is to understand if the enabler is statefull or stateless and then accordingly derive an architecture that provide it in ha and, following that, understand against which metrics (e.g. CPU load) to scale it up or down. following this work, we translate the derived pattern into a set of docker composer recipes (the idea is to be able to layer/compose them) now, while for certain GEri this is kind of straight forward (e.g. compare the work done for the context broker [1]) for others may be more complex and this require that the GEri has a way to share its state across multiple instances and this is documented. personally, I believe that we talk about maturity and quality testing of a generic enabler, this is a crucial aspect. a mature software is ready to be used in production environment, and to me that means that you can deploy it in such a way that you can ensure 99.9% availability of it. Best, Federico Dr. Federico Michele Facca Head of Martel Lab Martel Innovate Dorfstrasse 73 - 3073 Gümligen (Switzerland) 0041 78 807 58 38 0041 31 994 25 25 martel-innovate.com <http://martel-innovate.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170309/b4479385/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy