If you take a peek at the telecom world, you see a couple of big networking trends that are making waves there. However, changes are still slow to come, since network managers have a lot of legacy networks and infrastructure in place now. Ripping and replacing is expensive, time-consuming and risky. This expert thinks 2020 will be the year of actual hardware change for many telecom providers. At that point, the big technology changes will probably be around SDN, NFV, IoT and 5G wireless. The SDN trend will make sense to more telecom companies once virtual functions and switches are widespread in data centers and interoperability becomes easier. IoT doesn’t have a lot of obvious money-making potential right now, though 5G has the potential to create revenue as telecom providers offer faster links to customers. Like all technology choices today, the company’s bottom line will drive new network purchasing decisions.
This is the year that network IT pros should start getting to know IoT, says this expert. IoT is a network-dependent technology, so networking teams will be involved in any IoT initiative in their company, whether they know it yet or not. The wireless network in particular will be important, so the growth of 5G wireless will support IoT. It isn’t just the additional bandwidth that 5G can provide—it’s the ability of 5G to support many more devices with very low latency than previous wireless networks. Lots of carriers are also now moving to use low-power WAN technology that’s designed for IoT traffic, as well as an updated LTE standard. All of these developments require some research and cost/benefit considerations, but network teams will have some solid options when deploying IoT projects.
As the idea of the API economy edges into various industries, the idea of mapping applications grows too. It’s nearly impossible for IT teams not to be dealing with interdependent applications in this era of cloud-hosted and virtualized server infrastructure. It’s also common that IT teams don’t know about application dependencies until there’s a problem with a server or other piece of hardware that affects applications and leads to help desk tickets. The web of application dependencies at any given organization can be extremely complex. The rewards of mapping dependent components, though, come in easier troubleshooting and a paper trail for any compliance audits. We happen to know a monitoring tool that’ll give you a lot more visibility into cloud- and SaaS-based infrastructures.
Intel’s chip flaw continues to reverberate through IT departments. Rushed software fixes are helping the security issue, but causing performance slowdowns. One way to mitigate or avoid issues from the Spectre and Meltdown exploits may be multitenancy. Many of the big public cloud providers only offer multitenancy, where you’re sharing CPU space with many other users. But single-tenancy, either through a cloud provider that offers it or in your on-premises data center, allows you to avoid those performance hits that are affecting providers. In that controlled environment, you can leave the fix unpatched and keep both performance and security control. What would you choose?