Invited lecture on Software Engineering at UC3M on 25/11/2020.

1. Software Architecting at Scale
a practical walkthrough
Sergio Fernández
Senior Software Development Engineer (Amazon)
Universidad Carlos III de Madrid, 25/11/2020
Ingeniería del Software, Grado en Ingeniería Informática

2. DISCLAIMER:
The content in this presentation was created for
academic purposes. All the opinions expressed here are
my own and do not necessarily represent those of my
current or past employers.

3. Sergio
Fernández Some background about myself:
● Asturian Software Engineer
● Graduated from University of Oviedo
● Currently based in Vancouver
● Senior Software Development Engineer at Amazon
● Advocate of open technologies
● Member of the Apache Software Foundation

4. 4
Jan 2006: joined CTIC Foundation
Feb 2008: visited DERI (Ireland)
Aug 2017: joined Amazon (Canada)
May 2012: joined Salzburg Research (Austria)
Mar 2013: founded Redlink GmbH (Austria)
Dec 2006: graduated Bachelor Degree
Jul 2010: graduated Master Degree
Dec 2012: joined ASF
Feb 2015: lecturing at Fachhochschule
Salzburg (Austria)
Oct 2011: lecturing at ESNE
(University of Camilo José Cela)
May 2007: won 1st Free Software
University Spanish Contest

5. Outline for today
• Software Architecture overview
• Trends in software architectures
• Architecting software at scale
• Professional opportunities
• Q&A
5

6. Engineer
vs
Architect
Can anybody tell me what’s the difference?

7. Traditionally architecture is defined as
“the highest level concept of a system in its
environment. The architecture of a software
system (at a given point in time) is its
organization or structure of significant
components interacting through interfaces,
those components being composed of
successively smaller components and
interfaces.”
7

8. So… why does architecture matter?
https://www.flickr.com/photos/cuppini/48963256981

9. Martin Fowler defines it
“as a word we use when we
want to talk about design but
want to puff it up to make it
sound important.”
https://martinfowler.com/architecture/

10. Are Right, a Lot.

11. Desired
features of
any
software
architecture
● Feasibility
● Performance
● Reliability
● Testability
● Maintainability
● Extensibility
● Agility

12. The General Problem
https://xkcd.com/974/

13. Evolution of
Software
Architecture
https://twitter.com/richcampbell/stats/1078727465974067200

14. Scaling problem
Given a service with the following metrics on c5.2xlarge:
• concurrency=1, latency: p90=20ms, p99=100ms
• concurrency=10, latency: p90=120ms, p99=500ms
• concurrency=20, latency: p90=200ms, p99=700ms
• concurrency=50, latency: p90=800ms, p99=2s
• concurrency=100, latency: p90=1s, p99=3s
How would you scale it to 4,000 TPS (avg.) and 10,000
TPS (max.)?
14

15. 15
Monolithic SOA Microservices
Single Unit Coarse-grained Fine-grained

16. 16
The Rise of
Microservices

17. Architectura
l Patterns ● Client Server
● Layered
● Pipe and Filter
● Event Driven
● Microservices
● Peer-to-Peer
● ...

18. Handling increasing complexity

19. Distributed
overhead ● Continuous Delivery and
dependencies
● Integration testing
● New computation environments:
containers, serverless, etc.
● Data partitioning and consistency
● Messaging: queues, pubsub, etc.
● Logging and monitoring
● Networking: load balancing, service
discovery, etc.

20. Understanding the tradeoffs
20

21. “You build it, you run it!”
Werner Vogels, VP & CTO at Amazon.com

22. an architecture requires structure

23. Chaos Engineering

24. AWS Architecture Center: https://aws.amazon.com/architecture/
AWS Builders’ Library: https://aws.amazon.com/builders-library/

25. Amazon’s
Leadership
Principles
● Customer Obsession
● Ownership
● Invent and Simplify
● Are Right, A Lot
● Learn and Be
Curious
● Hire and Develop the
Best
● Insist on the Highest
Standards
● Think Big
● Bias for Action
● Frugality
● Earn Trust
● Dive Deep
● Have Backbone;
Disagree and
Commit
● Deliver Results
https://www.amazon.jobs/en/principles

26. www.amazon.jobs
26

27. Q&A

28. sergio@wikier.org
web
twitter
email