The document discusses the advantages and disadvantages of centralized versus decentralized architecture in a large organization like Allegro Group. Centralized architecture involves corporate projects and longer implementation timelines, while decentralized architecture focuses on local solutions and empowerment but may lead to duplicated efforts. The concept of federated architecture is also introduced, emphasizing local leaders with centralized support for better interoperability and the sharing of lessons learned.

1. Centralized
vs.
decentralized
architecture
Krzysztof
Dębski
Allegro
Group

2. Allegro
Group
>
500
people
in
IT
>
50
independent
teams
16
years
on
market

3. Naspers
Group

4. Centralized
architecture

5. Project
PMO
Analyst
Architect
Developer
PMO
Project
owner
ProducLon

6. Centralized
architecture
Corporate
projects
HR
financial
systems
common
messenger

7. Centralized
architecture
3
months
of
analysis
1
year
of
implementaLon
2
years
of
rollouts

8. Decentralized
architecture

9. Project
Architect
Developer
Project
owner
ProducLon

10. Project
Architect
Developer
Project
owner
ProducLon
Architect
Developer
Project
owner
ProducLon

11. Project
Architect
Developer
Project
owner
ProducLon
Architect
Developer
Project
owner
ProducLon

12. Pros
Less
wasted
effort
Empowerment
PracLcality

13. Cons
Locally
opLmized
soluLons
Duplicated
and
locally
cached
data
Local
compensaLon
for
other
projects

14. DDD

15. DDD
Core
domains
SupporLng
domains
Generic
domains

16. Federated
architecture

17. Federated
architecture
local
leaders
with
centralized
support
CooperaLon
between
domains
Local
soluLons
are
promoted
to
become
common

18. Lessons
learned
centralize
interoperability
decentralize
implementaLons

19. Lessons
learned
standarizaLon
is
overrated
you
won’t
have
single
plaXorm

20. Lessons
learned
reuse
is
not
about
code
sharing