Conclusion
Software-Defined Network. How it works and how to deploy. Part 2
Article REF: TE7611 V1
Conclusion
Software-Defined Network. How it works and how to deploy. Part 2

Author : Stéphane Litkowski

Publication date: May 10, 2017 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

4. Conclusion

In 2017, the technologies implemented in SDN architectures are very diverse and linked to specific use cases. It remains complicated to have an SDN controller that can manage all use cases. What's more, from an architectural point of view, this could also be a nonsense, as it could lead to problems of scaling, QoS management, etc. Indeed, the whole complexity of introducing central controllers will be to find the balance between functions to be centralized and functions to be distributed (as well as finding the right level of distribution). This balance will depend on each network and the associated services and constraints. The solutions on the market are diverse and non-interoperable today, although they are often based on certain standard protocol bricks. Their scope is also very varied, ranging from simple controllers with no real intelligence, to targeted applications (service chaining,...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Article included in this offer

"Software technologies and System architectures"

( 227 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details