Enterprise applications were quickly extincting ?

Time to spin off a new simple business process was taking more time than ever. Operations accused engineering accused QA accused business accused everybody and then they all went out and had a drink or two. Skippy the little dog who often was seen inside the office which belonged to nobody knows who, also rejoiced.

IT WAS AN Old jungle saying.. Architecture Matters and it is big.

Dark was the night and fearful the atmosphere.

Disruptions, innovative product releases killing legacy applications, enterprise chaos all reined the old town.

Does it really matter?

With vrooming engines racing to get the big byte of the Software Industry, it becomes important to roll out applications quickly. MVP's have shown signs of winning the battle. So how does architecture really matter?

If you build your foundations right, you will be able to:

a. Have a seamless integration outlet. This is important when you sell it to either other enterprises or collaborate. You want a system that is easily adaptable to other environments. Robust foundation architecture is key, for the aforementioned, to happen.

b. If you build on a feeble architecture, chances are that your application will either NOT scale, perform well enough or therefore the usage will be very negligible. More often, you wont' be able to bring up stability attempting to quickly fix because you now have a feeble architecture and fixing will take its own course. If you dig deeper into code you will realize that, building a robust foundation architecture helps in solving bugs. This philosophy applies to everything we said above.

.

Ok. Fine. You can exit this presentation. 

There is nothing being discussed here other than PURE ENTERPRISE ARCHITECTURE, standards, approaches and how to have a competitive edge. So if you are are not interested in the above, please feel free to leave this presentation.

.

Many People are building new applications that can disrupt functionalities of your enterprise application.  The "viral factor" can quickly become contagious and usage of your applications CAN DISASTROUSLY FALL IN NUMBERS.

What do you think ?

1 I don't believe in viral nature of applications that can disrupt our application.

2. I am not aware of anything that can disrupt our enterprise application.

3. Yes I know, such a thing happens often in today when there are new #startups sprouting every      second.

4. Yeah.. this tells me, I need to have coffee more often than never. Something along those lines.

The Architecture. 

Time and time again, analysts have shown the importance of building a strong foundation architecture.

Geoffrey Moore in his highly intellectual article "Systems of Engagement: IT Architecture in Transition" makes us understand the importance of a new way of architecture.

Excerpts from the article:

Systems of engagement represent a second architecture, one that developed independently from the client-server stack, and enterprise IT leaders now must find a way to interface the two. 

You can read this article here.

.

What did we understand? 

Didn't you read about the user-centric architecture? Don't you see how importance has been given in building robust, mobile based applications, using technology? Emphasis is what I am talking about.

Again, in an article on innovations, Mr. Moore explains how the different zones evolve and in that he again highlights the technology stack, thereby giving us the thoughts, "Is architecture the key factor"?

.

What can a feeble architecture do to you?

.

See ?

So it is to be understood that there are shark teethed coders out there who can bite off your face off, like Lecter Hannibal, of an otherwise good looking application by simply creating classic architecture. Often, feeble code in your application may cripple your client base and fuel user base in the just disrupted competitor. Users may simply rely on the other JUST FOR STABILITY and getting their requests completely fulfilled in split time.

Aha! Now that you have seen some kind of architecture diagram,  do you think, any further advancement of slides will be worth the time?

Ok. Then lets do some design thinking.

Did you know design thinking appears to be a way in which one finds resolution of problems and  creation of solutions, with the intent of an improved future result. 

You are persistent, aren't you?

Ok. Fine. Persistence is the sign of a successful individual. Ok. Let us try to come up with a robust architecture. Let me sum up. Here are few things you need to do.

1. Let us look at a future state of the enterprise IT
2. See, how disparate it is. Attempt a solution to make it less complex (Not less disparate)
3. Try and see the various processes that exist which contributes to the eco-system itself. Remember, you are not seeing a problem, rather you are defining a future state of the application.
4. Drop what I call as "hard stones" in places that you felt are good solution points or episodes.
5. Let us define endpoints and once we reach an endpoint, let us iterate over it.
6. NOW this is a turning point when you start to iterate.
7. Once you start seeing, more "hard stones"(Mentioned above)  , you will start your journey towards enlightenment.  

The problem is known, lets find a solution iterative-ly.​ Our future state of the application is robust. Secondly, the solution resides in first looking at the state rather than a particular problem. No we don't want to look at one performance problem.

Please feel free to run now. Design thinking, iterative-ly, don't look at performance.. uh! Go ahead. Please feel free to exit.

Your Goal

How many 'hard stones' did you place while on your path.

Your PATH is the future state. Call this as a SOLUTION.

Design it, iterate it, solve it.

Your Journey

Is your journey taking you towards enlightenment?

Are you placing more "hard stones"

Are you starting to see these "hard stones" starting to slowly shine and feels like diamond?

Well, you may be attaining your goal, THE SOLUTION, THE ROBUST FOUNDATION ARCHITECTURE. 

YES! THAT is right. you did the right thing, by advancing the slide. 

Because ---- The noblest pleasure is the joy of understanding.
                                                           ~Leonardo da Vinci

You know what?

I never learned from a man who agreed with me. -Robert A. Heinlein

END