I am a parent, futurist, and technologist. My career has spanned the birth of personal computers to the rise of cloud computing.
The Enterprise Resource Triangle (ERT)
Last week I posted three application migration or transition myths. I did point out in the article that while I listed three, there are many more. One of the things that I've noticed over the last 20 years or so of my IT career is more and more myths. Ultimately, watching application transitions and migrations fail led me to create the enterprise resource triangle(ERT). Regardless of where you build your applications, the three components of the ERT apply. But enterprise application should be considered differently from a consumer application in one sense. In the sense that the enterprise releasing or utilizing, sharing, or developing the application owns all three components. In the consumer space, it becomes a little bit more difficult. If you buy a phone from one company, and the application you're trying to use doesn't work on your phone, you can't call the phone company. They won't know the application at all.
My examination of the many limiting factors prompted the enterprise resource triangle's development and publications. The first is the device. I had a customer tell me that they only built iPhone applications for their employees. I didn't think about it at the time; I listened and moved on to the next thing. When I thought about it later, I realized why they only build applications for the iPhone. Apple has created a closed environment with Macintosh, the iPhone, and the iPad. Nobody builds operating systems for the Apple-controlled hardware. So building applications in that environment means you control some of the initial variables that impact application developers. In particular, it's how does the accelerometer work? How does the GPS chip work? By starting with an iPhone, you know those answers in the commonly published Apple development rules. So many organizations start the development efforts by leveraging and utilizing that closed environment. It's pretty straightforward to build the app. Androids can be cheaper and can be more customized. But the reality at one time or another was that there were more viruses available on the android store that existed in the iPhone world completely.
If you want your application to function in a somewhat closed environment, where you do not have to worry about many variables, build it on an iPhone. Suppose you need to create something that requires your ability to touch the operating system kernel that is different. Then you have to build it on an android phone. Accelerometer maker, GPS Chipmaker, and so on suddenly can impact your application. So you have to build the application on one Android phone type and not support the bring your device concept. The actual device you are using becomes important.
The ERT builts applications for tomorrow, today!
The enterprise resource triangle does have three angles; it's a triangle. The second is the landscape or the network. There are limits for and within networks. If you listen to television commercials, companies sell the fastest in-home Wi-Fi. But that's advertising. Sped to the device is a factor in network performance. Speed from the device to the router is also a factor. But, how fast the router can process the information and deliver it is also a factor. Speed applied to one part of the network will not help your application perform better. It is a 3 part consideration. First, how much data does the application generate? How much of that data is local (generated on the device) how much is remote (generated on the remote server). We need to know how much data does the device generates? How much data is the device consuming? And then ultimately, at some point or another, you have to worry about where the date is. By the way, you also have to consider the security of the data at some point or another. So how that device is connected is important. The fastest in-home Wi-Fi means from the router to your device that's as fast as it can get. It is not a to one relationship, however. There are three types of connections (on the device, on the server), and sadly, your application is not the only thing running on that device. The reality of the router cache can have a bigger impact on your application performance than the speed at which your router connects to your device. I.e., it becomes important to understand the rules. And again, ultimately, that's why I developed the enterprise resource triangle, to lay down my understanding of the various rules critical in application development and ultimately application migration and transition. If you do not consider the future state device your application is built for today when you move it to its brand-new high-powered cloud-based multi-server array, you may not get the performance gain you spent money to get!
The last piece of my triangle is the destination. Where is the data you are trying to consume? In the modern world, since around 2011, most larger consumer applications have moved to cloud-based. Enterprise applications have also begun the transition to cloud-based solutions. I've built a cloud pick up her customers, and in that, we talk about all of the requirements for performance within the cloud provider you select. I realized that the value of the cloud isn't that you pick a single cloud provider and put everything in that service. Rather, you consider what it is you need those applications to do and consider the power of each cloud provider independently. It's a little harder in the enterprise world to manage three cloud providers than it is to manage one. But if you can gain 10, 15, and even 20% performance by simply spreading out over multiple cloud providers doing different things, the value proposition becomes much higher. Multi-cloud is the future.
ERT-based application building becomes important when considering the migration and transition myths that will impact that application. Not Judy, the primary business focus myths I shared previously. There are significant performance myths that have to be dealt with as well. As I continue down the path of building out the enterprise resource triangle, I'll continue to share more and more functionality gains that organizations can benefit from in leveraging the triangle. The reality of application development is that someday that application will be transitioned or migrated. If your application is extremely successful, you may launch it and three days later be transitioning. It's important to remember that what you do today will completely make what you do tomorrow either useless or a win.
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.
© 2022 DocAndersen