Pages

Wednesday, 3 August 2011

Systems Architecture-Abridged

                                    The clock read 11.37 pm.I was busy face-booking and trying to complete a questionnaire simultaneously.The phone rang sharply and I not at all surprised to see that the call was from my younger sister Ricky .(She studies Computer Engineering and strangely enough,tends to remember all kinds of emergency work only during the late hours of night).Here goes the conversation thereafter:

Ricky : Hey..this is really urgent.I have a systems architecture internal assessment tomorrow and have no idea whatsoever.You need to tell me about it...and yes very concisely.

Me : Okk....since I don't have a choice...lets begin.In general , Systems Architecture refers to a visual representation of a collection of platforms(combination of hardware and operating system) and applications( software that runs on a platform and does a specific job) that reside on them.Also it is preferable to keep the data separate from the application.This leads to the concept of multi-tier applications.First,lets start with the simplest one:
  • Single-tier application: Here the data and the application resides on the same platform.This architecture works for single users but will be a problem if  multiple people need to access the same data.
  • Two-tier:Client Server Architecture:The common data is stored on a server and each user has a copy of the application i.e the business and presentation logic on his machine.Hence the name client-server.All these machines are connected by a Local Area Network which allows data exchange using TCP/IP protocols.The advantage is that the processing burden is not placed on the server .But again,the high bandwidth requirements slow down the application.In addition,maintenance and version control of distributed software is cumbersome.
Ricky : I get it...what next?

Me: Next comes the three tier and multi tier architectures:
  • Three-tier Architecture:The application is partitioned to station the business logic in a central location and the presentation logic on the client's machine and a database server at the back.Examples are SAP and Oracle eBusiness Suite.
  • Multi-tier Architecture:In this architecture,the client software on the user machine has been replaced by a web browser which communicates with the application server through an additional web server.

Ricky : What are its pros and cons?

Me : It is inexpensive as there is no need to invest in a corporate network.Also,specialized software is not required at each client location.But the business application needs to be web enabled and proper security software needs to be incorporated.
       Firewall servers serve the purpose and stand as gate keepers between the internet and the company's 
LAN.

Ricky : Is that all?

Me : Another important topic is Data architecture.Applications should be able to exchange data with each other.And data formats of applications should be compatible with each other.Hence the need for Integrated Database Systems.Advantages are no duplication or inconsistency of data and easy manageability.
       Next is the ERP System.Its positives are:Faster to implement,easier to manage,tighter integration across all functional areas and can be purchased as a single package from vendors.An modern ERP application when installed and deployed will be in a multi -tier web enabled mode.

Ricky : I  think I have learnt enough for my assessment.....

Me : Let me conclude with this...Database design and development is based on the relational model, examples of which are Oracle,SQLServer.Application design and development is done in programming languages like Java,C++,VB etc.

Ricky : Thanks a lot.

Me : No problem..but when you are free,visit the VGSOM website...http://www.som.iitkgp.ernet.in/ .This institute is where we have learnt all these from.Goodnight and all the best for your exam.

Ricky: Good night



       

No comments:

Post a Comment