-
(1) pragmatism,
-
consider - v1/v2.
-
macro- vs micro- services vs ... (monorepo),
-
Patterns:
- observability (from the customer perspective),
- reverse proxy,
- load balancers (round robin/sticky),
- queues / pub sub,
- caching,
- CDNs.
Warto wykształcić wrażliwość na kod, który może być nie wydajny:
- https://app.codility.com/programmers/lessons/1-iterations/,
- co u mnie się kiedyś sprawdziło, template projektu.
- functional tests, e.g, unit tests, integration test (a part of CI/CD),
- API end2end (periodical happy path tests on the prod),
- performance tests (e.g., locust or gatling),
- iterations (+ retro after more complex implementation).
Do not forget about:
- internal demos for designers/product people,
- feedback from customers.