The document outlines the evolution of enterprise application architecture over the last 30 years, highlighting the transition from monolithic systems to modern cloud-based and IoT architectures. It discusses the need for system architects to balance creativity with scientific principles and adapt to changing business demands through tiered architectures and service integration. The evolution reflects a shift towards modular, highly coupled systems that leverage open standards to support global business complexities.

1. The Evolution of Enterprise Application Architecture
30 YEARS IN 15

2. theneedofevolution
•
global customersandworld widecompanies
•
shorterbusiness timing
•
based systems platforms
•
valuebusiness integration
•
new systems propositions:
•
behavior, feel, share, moments, wear, play, life, ...
theevolutionofenterpriseapplicationarchitecture

3. •
design tomeetsystem requirements;
•
createthesystem ‘blueprint’;
•
define how the components communicate;
•
balance the "creativity" with "science" using models, frameworks and patterns;
•
break down the system complexity;
theneedofsystem architect
theevolutionofenterpriseapplicationarchitecture

4. thecube distributionarchitecture
partition the behavior of the application into tiers
properly use the services of each platform
give preference to open standards and maintained by ‘good’ players
theevolutionofenterpriseapplicationarchitecture

5. past, presentandfuture
70´s
2 k
2015
2020
monolithicapplications
client-server applications
web-basedapplications
cloud-basedapplications
(IaaS, PaaS, SaaS)
CAMSS-basedapplications(Business As Services)
service-basedapplications
IoT(Internet ofThings)
theevolutionofenterpriseapplicationarchitecture

6. •
monolithicapplicationarchitecture(70´s)
present
theevolutionofenterpriseapplicationarchitecture
few users
high modularized & coupled
on-line / off-line processing
data staging processing
procedural languages
high optimized hardware
medium complexity

7. •
client-server applications(90´s)
past
theevolutionofenterpriseapplicationarchitecture
few users
low modularized & high coupled
on-line (lan) (synchronous)
database processing
procedural languages
low optimized hardware
low complexity

8. •
web-basedapplicationarchitecture(2k)
present
theevolutionofenterpriseapplicationarchitecture
many users
high modularized and low coupled
Internet (synchronous)
distributed processing
object languages
high optimized hardware
medium complexity

9. •
service-basedapplicationarchitecture
present
theevolutionofenterpriseapplicationarchitecture
many processes to integrate
very low coupled
Internet (synchronous/synchronous)
distributed processing
object languages
composite applications
high complexity

10. •
cloud-basedapplicationarchitecture(CAMSS*)
present
theevolutionofenterpriseapplicationarchitecture
many processes to run
very, very low coupled
cloud computing (Paas+SaaS)
improved security
service applications
global businesses
too much complex
* Cloud, Analitycs, Mobile, Social andSecure

11. •
IoTapplicationarchitecture(Internet ofThings)
future
theevolutionofenterpriseapplicationarchitecture
device-based applications
very, very low coupled
embedded computing
low security
global businesses
multi languages
expensive R&D

12. putin alltogheter
theevolutionofenterpriseapplicationarchitecture

13. The Evolution of Enterprise Application Architecture
30 YEARS IN 10
Oziel Moreira Neto (oziel.neto@gmail.com)
Q&A