2013 Second European Workshop on Software Defined Networks 2013
DOI: 10.1109/ewsdn.2013.13
|View full text |Cite
|
Sign up to set email alerts
|

On the Feasibility of a Consistent and Fault-Tolerant Data Store for SDNs

Abstract: Maintaining a strongly consistent network view in a Software Defined Network has been usually proclaimed as a synonym of low performance. We disagree. To support our view, in this paper we argue that with the use of modern distributed systems techniques it is possible to build a strongly consistent, fault-tolerant SDN control framework that achieves acceptable performance.The central element of our architecture is a highly-available, strongly consistent data store. We describe a prototype implementation of a d… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
40
0
3

Year Published

2015
2015
2023
2023

Publication Types

Select...
5
3

Relationship

1
7

Authors

Journals

citations
Cited by 49 publications
(43 citation statements)
references
References 13 publications
(13 reference statements)
0
40
0
3
Order By: Relevance
“…Other proposals that try to define interfaces between controllers include Onix data import/export functions [7], ForCES CE-CE interface [30], [211], ForCES Intra-NE cold-standby mechanisms for high availability [212], and distributed data stores [213]. An east/westbound API requires advanced data distribution mechanisms such as the Advanced Message Queuing Protocol (AMQP) [214] used by DISCO [185], techniques for distributed concurrent and consistent policy composition [215], transactional databases and DHTs [216] (as used in Onix [7]), or advanced algorithms for strong consistency and fault tolerance [213], [198].…”
Section: Eastbound and Westboundmentioning
confidence: 99%
See 1 more Smart Citation
“…Other proposals that try to define interfaces between controllers include Onix data import/export functions [7], ForCES CE-CE interface [30], [211], ForCES Intra-NE cold-standby mechanisms for high availability [212], and distributed data stores [213]. An east/westbound API requires advanced data distribution mechanisms such as the Advanced Message Queuing Protocol (AMQP) [214] used by DISCO [185], techniques for distributed concurrent and consistent policy composition [215], transactional databases and DHTs [216] (as used in Onix [7]), or advanced algorithms for strong consistency and fault tolerance [213], [198].…”
Section: Eastbound and Westboundmentioning
confidence: 99%
“…An east/westbound API requires advanced data distribution mechanisms such as the Advanced Message Queuing Protocol (AMQP) [214] used by DISCO [185], techniques for distributed concurrent and consistent policy composition [215], transactional databases and DHTs [216] (as used in Onix [7]), or advanced algorithms for strong consistency and fault tolerance [213], [198].…”
Section: Eastbound and Westboundmentioning
confidence: 99%
“…averaging about 1 KB. and no more than 4KB [17] . So the number of communication times per unit time can be used as a measure of communication overhead [18] .…”
Section: Communication Overheadmentioning
confidence: 99%
“…Consequently, this definition encompasses concepts related to availability -an indicator of whether a service will be present when requested -and reliabil- Botelho et al [37] Kempf et al [40] ity -a measure of continued operation for a specified period of time. Also, dependability relates to measures of safety, integrity and maintainability;…”
Section: Resilience Disciplinesmentioning
confidence: 99%
“…Botelho et al [37] treats the consistency between a network controller and their redundant backups, focusing on performance aspects. The main conclusion of the authors is that strict consistency and fault tolerant systems can operate with acceptable performance.…”
Section: Fault Tolerance and Survivabilitymentioning
confidence: 99%