SpringOne 2020 Software Architecture: A Story About Business Value and Tradeoffs Abel Fresnillo Silva, Senior Software Engineer at Lowe's Companies

1. Software Architecture
A story about business value and trade-offs

2. About me
• Senior Software Engineer
• 15 years of experience building,
architecting solutions and leading
development teams
• Passionate about software
development stuff
https://cltjug.org

4. Understand what business value means for
your organization

7. What and Why Architecture

8. What and Why

9. One of the biggest
tragedies in the software
world is the divorce
between business users
and technical team.
- Martin Fowler

10. Know your customer

11. Lean Cycle
Learn
Build
Measure
Data
Ideas Product

12. Event StormingValue Stream Mapping

13. What and Why Architecture

14. Architecture

15. • Strategic Goals
• Domain considerations
• Architecture characteristics
Fundamentals of Software Architecture
Neal Ford / Mark Richards
Choose an architecture style

16. Step 1
Choose Architectural Characteristics

17. We want to expand
our business to
other countries
Security will always
be first in our list of
concerns
We want to support
multiple players
during peak hours

18. Architectural Characteristics
Scalability
Portability
Security
Usability
Durability
Evolvability
Reliability
Traceability
Agility Resilience

19. Step 2
Monolithic vs Distributed

20. Catalog

21. Monolithic vs Distributed
Catalog
Availability
Correctness
Durability

22. Monolithic Architecture Styles
Layered Architecture Modular Monolith

23. Monolithic Architecture Styles
Catalog
Availability
Correctness
Durability

24. Catalog
Availability
Correctness
Durability
Product CatalogUser Interface
Reporting
Accessibility
Simplicity
Usability
Accuracy
Integrity
Reliability

25. Microservices Architecture
Distributed Architecture Styles
Event-Driven Architecture

26. Step 3
Determine Architecture Quantum

27. Catalog
Availability
Correctness
Durability
Product CatalogUser Interface
Reporting
Accessibility
Simplicity
Usability
Accuracy
Integrity
Reliability

28. Step 4
Determine Persistence

29. Catalog
Availability
Correctness
Durability
Product CatalogUser Interface
Reporting
Accessibility
Simplicity
Usability
Accuracy
Integrity
Reliability

30. Step 5
Determine Communication Style

31. Catalog
Availability
Correctness
Durability
Product CatalogUser Interface
Reporting
Accessibility
Simplicity
Usability
Accuracy
Integrity
Reliability

32. What and Why Architecture

33. Focus on the problem!
The most important tool is
you… figure out what tools
makes sense and leverage
them to solve the problem
- Kelsey Hightower

34. https://martinfowler.com/articles/value-architectural-attribute.html
https://leanpm.org
https://www.eventstorming.com
http://fundamentalsofsoftwarearchitecture.com
References

35. Q & A
https://abel.dev
https://github.com/abel-fresnillo
@abel_fresnillo
me@abel.dev