Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Evolution of Software Architecture
Transcript of Evolution of Software Architecture
More expensive Upgrade
Concurrency - the database is limited to the number of users Client/Server More concurrency
More points of failure Division and reuse logic
Independence from the database
Data access scalability
Reuse more level
Slow cost of customer management Single protocol
More processing on the server
Failure points increase
Overload on the server (because the database languages and database must run on the same server which limits the scalability) More security (centralized access, integrity on the server)
Better software maintenance Scalability at the hardware level
Less idle machines
Less loaded machines Multitasking Cost More processing Failure points Failure points Fault recovery Traditional Software Architecture . High security
. Secure data Client/Server compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS ADVANTAGE PROBLEMS / LIMITATIONS compared to the previous compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS Present v1 Present v2 Classic Spaghetti Code ADVANTAGE PROBLEMS / LIMITATIONS Concurrence Spaghetti Code Low maintenance
Low cost Client/Server Wyse Initial Fat Client (Logic in the client)
Fat server (Logic on the server as stored procedures)
Less expensive GUI
Single point of failure Logic in the client
Logic on the server as stored procedures
High maintenance GUI
Number of terminals
Single point of failure
High maintenance compared to the previous Cloud Computing Spaghetti Code Access to computing power at low cost
Improve the performance of computer equipment without purchasing new equipment
Unlimited increase space for storing data and information of an organization or an individual compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS Dependence on internet access
Security and privacy of data in case of theft of password swith out purchasing new equipment
loss of control of data files as these would not be accommodated in the client computers but in the cloud More concurrency
More points of failure compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS compared to the previous ADVANTAGE PROBLEMS / LIMITATIONS Group Members
OSCAR JAVIER ARDILA
LUIS EDUARDO SOLANO
VERMEN RAINER AYALA
LUIS RAUL MULATO MILLAN, MSc.
February 9, 2013 More points of failure