I am a long-time Futurist, and technologist. In my career, I have spanned the birth of personal computers, to the rise of Cloud Computing.
Let's expand on the Enterprise Resource Triangle (ERT)
I talked a lot about the enterprise resource triangle for the last few weeks. And I did want to point out that it is not something completely new. It is building on the concept of the resource triangle. It is a modification and something new. However, the packaging and the theory in the expression of the enterprise resource triangle are completely mine. It's a solidification of my 30 years of I.T. experience into a single unifying structure. In this article, I would like to go a little further into the concept behind the enterprise resource triangle—the first component being kind of a review. We talked previously about consolidated enterprise resource triangle applications, either consolidated or distributed in the world of edge computing solutions. The Enterprise resource triangle (ERT) doesn't only apply to edge applications; however, I bring up edge applications again and talk about the previously because edge applications lend themselves very effectively to the concepts of the enterprise resource triangle.
If we take a deep dive, and that's the article's goal into each of the three parts of the triangle, we will begin to see why each part has evolved radically over the last few years. I'll start with the device. In the last ten years, the device has evolved to being predominantly cell phones. I know I published a while ago an article asking when the cell phone would replace the laptop. By the end of the article, I realized that it doesn't matter if content creators continue to use laptops and desktops for the next thousand years. The reality is the vast majority of users that are consuming Internet services use their cell phones. The cell phone is the predominant device. By it's important when we consider devices that we consider the capabilities and limitations of all the devices in question. For example, applications baked in have less capability than the cell phone in presenting those applications. It's about the inputs from and to the device. If you think about the device as a limitation, how do I get data into the device? So as you begin the look at applications in your I.T. organizational portfolio, you have to consider how are people inputting information into this application.
Author's Note: If you build an application consumed by field professionals that don't consider edge computing, you'll have to rebuild the application in less than two years. But, if you deploy an application that requires keyboard entry and the majority of its users are using a cellphone, you'll have to rewrite that application almost well immediately.
Our next step is to consider the applications in your enterprise portfolio. How do users connect to that application today?. I have told many CIOs that you can create the greatest application ever written in the last few years. It can be so perfect that everything in that application works better than any other application ever built. But sadly, applications are not a field of dreams. If you build them, people can't necessarily come to them. You see, you have to have the Landscape. And the Landscape has evolved a lot. 3G became 4G, Wi-Fi five became Wi-Fi six, and now 5G and Wi-Fi six are more and more prevalent. You have to understand what your Landscape can do, and the Landscape will continue to expand and offer even more services. The Landscape today is still evolving beyond the reality of 5g, or Wi-Fi6. The network is changing. Now the Landscape Is moving towards SD-WAN, or software-defined networking SDN lies a whole world of huge improvements and what networks can do. The other side of SD-WAN lies was called an AAS or network as a service. On the other side of the network as a service lies the most exciting potential change to the world of landscapes that happen well since the addition of data to the cell phone—the concept of application-aware routing. Application-aware routing and faster cell phones will create a whole new world when just the device is in the Landscape. But it is a triangle, and the third piece is critical to, in fact, maybe all three should be defined as equal.
To move from where we are to the brave new world!
It is really interesting to look at the triangle, the device, Landscape, and destination. Ten years ago, the concept of destinations changed forever. While out in the market for about ten years, the smartphone had not yet reached its current status. 64-bit processors have only been in smartphones for the last five years or so. Networks were bound to 4G and then 4G LTE. While at the same time, the cloud was becoming ubiquitous. The three primary cloud delivery models within the cloud IaaS, PaaS, and SaaS were known and available ten years ago. They continue evolving at a rapid rate. We moved from traditional machine-based cloud solutions to serverless cloud solutions. The destination continues to increase in capability. Destinations today now have three distinct flavors (cloud, colocation, and on-premise).
The Enterprise Resource Triangle helps you balance your application portfolio as an I.T. or business, or even government. The ERTt allows you to consider applications as delivering information across all three aspects of the triangle. Inside of the triangle is the future state. And that is where organizations can offer managed, connected, and secured solutions based on all three legs of the triangle. It's going to change application development in the future. The application of the triangle will allow I.T., consumers, and of course, government entities to build applications that are smart enough to be aware of the three edges of the triangle. And in the core of the triangle delivering that managed, secured, and connected future. The advantage for the I.T. shop in using the triangle is that applications will live within the resources and capabilities available today with an eye towards what's possible tomorrow. As a futurist by dream is that everything builds today will work tomorrow. As a realist, I know that half of the things built today will not work tomorrow.
As we move into the world of edge applications, serverless cloud applications, and all other forms of applications, we will begin to see the evolution and value of the ERT. Many years ago, I was part of the client/server revolution. Now I'm lucky enough to be part of the ERT revolution. Honestly, it is what we all kind of thought client/server would be. As we head towards the future of devices, landscapes and destinations, remember the ERT. Create a balance on all three edges of your enterprise portfolio. Then when the time comes to upgrade solutions, remember to evaluate all three parts of the ERT!
This content is accurate and true to the best of the author’s knowledge and is not meant to substitute for formal and individualized advice from a qualified professional.
© 2021 DocAndersen