Complexity of WAN Optimization, Application Acceleration devices makes analysis of problems and root cause analysis more complex. Yes, they are beneficial, but if you have an issue only the manufacturer has the ability to fix the problem. Sadly not much motivation exists for them to help you determine that the esoteric problems you have manifesting are related to the devices.

Transcript for this Video

The four major areas causing IT Complexity Acceleration.

1.) Technology
2.) IT Silo / Dept Growth
3.) Personnel Specialization
4.) Out of Sight – In the Cloud!

Hi, I’m Bill Alderson and welcome to a little session on IT Complexity Acceleration.

Thanks for stopping by today. I’d like to talk to you about the issues affecting IT Complexity and its Acceleration. First of all what do we have? We have technology. Every area of technology is getting more and more complex. Now sometimes it makes it better; less problems and that sort of thing. But there’s a lot of new technology out there that’s actually making things much more complex- Multi-tier applications SOA interfaces. That’s interfaces to other people’s data that you’re bringing into your application.

You’ve got WAN optimizers you’ve placed in between your client and your serve; additional devices that are taking the data, compressing it, encrypting it, optimizing it for certain applications. For certain applications it’s on, for some applications it’s off. Sometimes it works well, sometimes it doesn’t work well. But let me tell you when there’s a problem there’s a problem and it requires detailed analysis.

Why do you think that Riverbed, maker of WAN Optimization, Application Acceleration appliances bought all of the developers of Wireshark? – Because they had to! The complexity of the WAN Optimization, Application Acceleration technology is vastly accelerated beyond native client server architecture. Used to be you could see every router, every switch, and every device between the two. Now you put in these very quiet WAN optimizers. You also have other things like load balancers. Those load balancers go in between the servers and the clients. So when you do a TCP connection you connect up to the load balancer. The load balancer then sends another request on a separate TCP port, another OSI model and goes to the server.

So you’re really not interacting from client to server. You are interacting from client to WAN optimizer, WAN optimizer to load balancer, from the load balancer to the server- vastly more complex. In addition, we have on the network interface cards and all of our devices; we now have TCP offload engines in order to be able to do more with the processor on the board and take away from the processor in your CPU of your hosts and of your clients. So the TCP offload engines are taking that and putting them in the offload. That’s yet another set of complexities, another set of dynamics to where you’re not truly communicating from the client to the server.

We’re in a day and age where we’re buying lots of monitoring tools and systems and equipment. We have a plethora of men in the middle. I call them “Our man in the middle”, those load balancers, and those TCP offload engines. Then you have firewalls. Sometimes the firewalls are actually taking sessions from the client to the server and in between changing TCP options.

Well all of these things are good, but, if you don’t have analysts who can really look at this data when something goes wrong, you can’t really troubleshoot until you get the next round of what?- Forklift upgrading. That’s what the vendors are counting on, typically. We’re doing very little to optimize what we have today. Everything seems to be having to be attached to a new technology before we’ll do anything. So there are many free options to optimize, to tweak, and to improve the relationship between the client and the server. Those load balancers, those WAN optimizers and all of these different things we can optimize if we take the time to do it. And we can get huge ROI, huge bang for the buck by using brain cells to analyze things instead of just budget to buy new stuff.

Your IT silos, your departments are growing, your budgets are greater, there’s more complexity, there’s more dependency. Because of those greater budgets we have more differentiated silos so we’re diversifying our budgets even more. In between those silos are walls that go up. When there’s a problem from client to server and you’ve got the desktop, the firewalls, the network, the load balancers, the WAN optimizers, the servers, you’ve got the applications and now when there’s a problem- who do you go to?

There are very few generalists who know and understand your entire architecture. In fact that’s the next topic here. We’ve got personnel specialization. All of our folks are becoming like doctors. They have more and more vertical specialization so when you have a problem that’s from client to server and somewhere in between you have to assemble a huge team of people to basically address all the various issues associated with that technology. There are very few people who really understand from client to server and all points in between. You have very few generalists today and a lot of knowledge is hidden from them because the silos are defensively hiding information from one another so that no one can accuse them of a problem. So it’s a growing divided support group problem because of personnel specialization.

And last, but definitely not least, an emerging growth trend is the move to the Cloud. What do we have? We’ve got remote data centers; we’ve got data centers that are being consolidated. We have fewer of them and they’re further away from us. They’re lights out. There’s less knowledge, less intimacy and less interaction with the technology. It’s a separated support group from who usually takes care of those things. It’s a lights out operation. Everything has to be done virtually. And if it has to be done virtually, that means documentation must be at the very highest ability and highly collaborative; which is more than likely a problem, again.

So here are some things that will help you with this IT complexity acceleration. Number one: Take a look at Architecture Ownership. I have some pieces I talk about in my best practices about Architecture Ownership on our Apalytics’ website and Apalytics’ YouTube Channel. Number one in Architecture Ownership is ‘know yourself’. That means that you document your systems, you document your network, you document where those load balancers and WAN optimizers are. You document both sides of them so people can see how their packets are being treated. You document your net QOS, your quality of service metrics. Everything is documented so the technologist who’s trying to look at an end-to-end communication session knows exactly what’s affecting their packets and their systems.

After you have documented your system and it’s very good and it’s highly collaborative you need to train everybody and certify people on your architecture. Don’t let anybody into your sight or don’t let anybody have the keys to your servers and your routers and your switches and that sort of thing until they truly understand your architecture. That is only done by showing them the diagrams, showing them your architecture, showing them the packet flow, showing them the application flow so they are fully understanding of the client to server before they get in there and start tweaking things and changing things.

That change that you’re having problems with, I know, you don’t like change anymore because it imputes problems into your environment. I totally agree. But if you have people who understand all the pieces of the puzzle across all the business silos and understand end-to-end transactions you’re going to be much better off in that capability. Architecture Ownership- take a look at my Best Practices on it.

Second: Decision Support Metrics. Decision Support Metrics allow you to find out if I upgrade that server, if I upgrade that database, if I upgrade that network connection, if I update that SAN, what is it going to do exactly for the response time of my mission critical application? Is it going to go from 25 seconds to 18 seconds? Is that what it’s going to do? If you don’t know, then why are you spending millions of dollars on it if you don’t have quantification? Maybe you don’t have any Application Performance Management, APM, in your environment? Maybe you’ve bought all to those tools but they’re actually not working? Maybe your help desk can’t even use them? So you can buy tools and you can buy systems but if your technologists are not using them…. So they may be bought by one of your IT silos but not shared in the other silos so that they can gain the benefit of the understanding. Your tools should have an end-to-end cross technology, cross silo view to them.

The other thing is your silos. There are walls are growing around them. Business Technology Integration: the building of virtual groups so that you basically take a look at network documentation and metrics across the entire enterprise- not just within a silo. So right now if you go out to your silos they all have documentation but nobody has typically an end-to-end view of how the end user is affected. All these silos are being plotted and they’re doing wonderful work and that sort of thing- but if you talk to the end user community and the business unit folks who are impacted by slowness and intermittent problem and that sort of thing you get a different picture, right? Okay, I know it because I hear it, I see it, I feel it, I talk to people, and I get called in to solve these problems.

You need virtual teams to deal with documentation, metrics and optimization of your environment. Now you need a Master Plan so I’ve got some stuff on Master Plan Development on the website- go take a look. And lastly, Application Optimization during development and operations: You need to take a look at your systems from end to end. Find out what your transactions are doing. Tweak your metrics so that they are pinpointed and getting signatures of your application performance.

Well that’s enough for today about IT Complexity Acceleration. Join our communities. Let us know what you think about these videos and the information. Really these pieces of data are valuable if you take a look at them and you think about them and you integrate them into your mind and your thinking- you’ll be a very successful IT Executive and Chief Information Officer.

I appreciate you stopping by. I’m Bill Alderson and my very best to you today.

 

Share This