Controller architectures must consider how state information is going to be collected, stored, and accessed. SDN applications need to be designed with state consumption in mind. Which decisions does the application need to make, and more important, what are all the data sources required to inform those decisions? Even the devices themselves will be part of the solution. How should they publish data related to the current conditions on the device to be used by these applications? Given the uncertain architectural landscape, what can be done on devices to make the eventual integration with other infrastructure easier?
Obviously, there are more questions than answers at this point. But in our industry's rush to get point protocols and solutions to market, we are in danger of solidifying architectural principles without fully considering the endgame. We would all do well to pause now and ensure we're planning for long-term success.
New Tech Forum provides a means to explore and discuss emerging enterprise technology in unprecedented depth and breadth. The selection is subjective, based on our pick of the technologies we believe to be important and of greatest interest to InfoWorld readers. InfoWorld does not accept marketing collateral for publication and reserves the right to edit all contributed content. Send all enquiries to firstname.lastname@example.org.