enterprise application framework

Hussain [email protected]

WebOSS ‘08http://www.hussulinux.com

Enterprise Application Frameworks

Products Strategies Best Practices and more



Why you need Frameworks?

People come and people go..

All kinds of people

Standards

Business Continuity



Fresh water lake

A Business is like a fresh water lake, People come and people go.

And it should be that way…



Various kinds of people

With Business knowledge Typically a BA

With Technical knowledge Developer, tester

With Both System Analyst

Without Both Manager!



Standards ‘A’ coded in C ‘B’ coded in C++ ‘C’ coded in Java ‘D’ coded in C# ‘F’ coded in Ruby ‘E’ just joined

If well integrated, it makes a fine hybrid system, ‘E’ has to be trained

Else ‘E’ has a big problem!



BCP(Business Continuity Process)

The show must go on!



Setting up an Enterprise App Framework?

People

Technology

Processes

Hardware

Software



People

Choose the right guy

Wrong person or cheap labor may screw your business

Extra efforts Remember Time = Money?



Technology

Choose one , choose many but choose wisely

Look out for availability more than features.

Don’t let technology drive your business, look for flexible alternatives

Always think about cost too.



Processes Anything done in a well defined process,

executes well.

A well defined process will take care of risks and mitigation plans

No one should be allowed to run away from processes but yes, processes should be flexible.

Again, never let processes hamper the business, remember they are to help you!



Hardware Infrastructure

Rented hardware Vs Purchased

Cost Vs Performance

Usage Vs Time



Software Infrastructure

Performance & Features

Implementation

Security

Cost



Technical Requirements

Typical 3-tier architecture. Things will never change

User Interfaces

Middleware/Servers

Backend Databases



What will change

User Interface? Web Interface – Web 2.0 Buzz

Desktop Software – legacy

Mobile – Upcoming

EAI (Enterprise application Integration)



Middleware / Servers

Web server Apache, Tomcat, JBoss IIS Custom

Messaging server JMS EMS



Databases

Various Databases Adapters Database Independence?



Standards

Infrastructure standards PC/Laptop standard software File sharing/emailing

Technology Best Practices Using the right resources QOS



Business Continuity

The show must go on!

Backup and Disaster Recovery? Database/Files Installed Software Emails? Any other necessary



BCP

Human Resource Backup and DR Are you Technologically Challenged?

Members with less technical knowledge. Gap between business and technology? High training and KT cost / Time?

Individual show? Single person controlling the wheel

Team with all experts – Balance? Do you have team with all experts in all technology Or a team with all experts in individual technology



Conclusion

Choosing a Technology? Do consider these factors:

Cost of product / Open source solution? Cost of training ? Cost of Infrastructure and Implementation Availability of resources / Docs Availability of Support



Conclusion

Choosing a Technology? Don’t (s):

Fashion / Trend: Don’t choose because others choose it.

Don’t stick to Legacy systems. Keep evolving. Don’t compromise on cheap labor. Quality is

important. Open source is NOT always the best Don’t depend a lot on vendor too: They always

charge you for every little extra thing!



Open House

Queries ?

enterprise application framework

Technology

cost of infrastructure

business knowledge

individual technology

best dont

cost of training

various kinds of people

kt cost time

dont stick