search

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.
Apache License 2.0
1 stars 0 forks source link

Messaging Node should be resilient #35

Open acheambe opened 9 years ago

acheambe commented 9 years ago

when operating under overload situations or failures, in general.

pchainho commented 9 years ago

@acheambe what do you mean by "Service assurance management"?

pchainho commented 9 years ago

I've removed the "security part" since it is alraedy on #34

acheambe commented 9 years ago

Service assurance management is the enforcement of policies and processes by CSPs to ensure that services offered over networks meet a pre-defined service quality level for an optimal subscriber experience. This is used to identify faults in the network and resolve these issues in a timely manner so as to minimize service downtime.

In the case of the MN, this may include the following:

pchainho commented 9 years ago

this sounds like a big requirement per se

acheambe commented 9 years ago

Yes. It was somewhere in the DoW. We can re-define with min requirements. Just "Resilience (operate under load, failures, and attacks)" should be enough

frankob commented 9 years ago

Unclear to me: the Messaging node will be in state of the art Networks/Domains a functionality, which is normaly provided by the CSP. If we don't want to force existing CSPs to completely restructure their infrastructure for the case that they are willing to follow the reTHINK Approach, we should not overload the Messaging node with functionality. But this is the old question: should rethink provide an add on to extisting architecture, networks/Domains, where the CSPs have the possibility to add interoperability with little effort and without the Need to replace the whole existing infrastructure or does reTHINK define a completely new infrastructure where a CSP is forced to replace his whole infrastructure in order to be able to follow the Approach. In the second case I am pessimistic that the Approach will enter the market.

pchainho commented 9 years ago

as it is currently defined, and thanks to protofly, the reTHINK arch does not impose any specific solution for the message node, thus CSPs are free to re-use existing solutions if it suits its needs