Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

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.

No, thanks

Evolution of Software Architecture

Evolución de la Arquitectura de Software
by

Alexander Guerrero

on 9 February 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Evolution of Software Architecture

Evolution of Software Architecture Evolution of Software Architecture Monolithic Applications ADVANTAGE PROBLEMS / LIMITATIONS Client/Server Client/Servidor (3 layers) Multitask Massification Virtualization Low security (data) More processing
More GUI
More multitask
More expensive Upgrade
Concurrency - the database is limited to the number of users Client/Server More concurrency
More protocol
More maintenance
More points of failure Division and reuse logic
Improves scalability
Independence from the database
Data access scalability
Reuse more level
Slow cost of customer management Single protocol
More processing on the server
More concurrency
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
Fault recovery
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)
More processing
More GUI
Multitasking
Less expensive GUI
High maintenance
Single point of failure Logic in the client
Logic on the server as stored procedures
Concurrence BD
High maintenance GUI
Number of terminals
Multitask
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 protocol
More maintenance
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
ALEXANDER GUERRERO
LUIS EDUARDO SOLANO
VERMEN RAINER AYALA
ROSAURA GUTIERREZ

PROFESSOR
LUIS RAUL MULATO MILLAN, MSc.

February 9, 2013 More points of failure
Full transcript