Building a sustainable Architecture

The ideia is to show how can you have a sustainable codebase when working with hexagonal architecture, tests and functional programming.

Transcript

1. Building a sustainable architecture
2. Why do we talk about architecture?
3. High maintainability Low tech debt
4. Basis for communication
5. Earliest decisions
6. Maintainability is a long- term concept
7. Hexagonal Architecture
8. Tests
9. Functional Programming
10. How does hexagonal architecture, functional programming and tests lead to a sustainable architecture?
12. Hexagonal: Main ideia
13. Executed by different actors
14. Tests in isolation
15. https://fideloper.com/hexagonal-architecture
16. Everything depends on the domain, the domain does not depend on anything
17. Separates problems
18. Goals
19. Shell for the domain
20. Safe to switch technology
21. Layers
22. Domain model
23. Ports
24. Adapters
25. Tests in hexagonal architecture
26. Mocking
27. Dependency Injection
28. Benefits
29. Focus on what matter most
30. Simplify the architecture
31. Easier to test in isolation
32. Ports and adapters are replaceable
33. High Maintainability
34. Drawbacks
35. Not declarative
36. Tests
37. Feedback
38. Accuracy
39. Reliable feedback
40. E2E Problem
41. No more end-to-end tests
42. Think only a little larger
43. Microservices
44. Providers & Consumers
45. Contract Tests
46. Speed of feedback
47. Why highly testable code?
48. Functional programming
49. "functional programming is a programming paradigm—a style of building the structure and elements of computer programs—that treats computation as the evaluation of mathematical functions and avoids changing-state and mutable data" Wikipedia
50. Functions from math
51. Methods Functions Procedures
52. Pure functions
53. Functions, inputs and outputs
54. Immutable data
55. Referential transparency
56. x = bestNumber[29, 9]
57. Hard things OOP Easy things FP
58. Boundaries
59. Isolation
60. Why isolation is a problem in OO?
61. Isolation is the dual of encapsulation
62. Why it is hard to balance between isolation and encapsulation?
63. Not a problem in FP
64. Hexagonal architecture in FP is natural
65. Push impure code to the boundaries
66. Good FP design is ports and adapters
67. Thanks!!!
68. We are hiring!!! https://nubank.workable.com
69. https://github.com/carolpc https://twitter.com/CarolinaPascale carolina.pascale.c@gmail.com WHERE TO FIND ME