garrardkitchen / blog Goto Github PK

Content:

• Kick towards the end goal
• No code is perfect and will continually change
• Don't be precious of codebases
• Better results and less code when dev is driven from tests in a TDD approach
• Get POs - if developing FEATURES, to provide tests!!
• Don't code for resilience on serverside, let arch deal with it - EDA - show fav pattern here
  Client validation as well as server-side validation
• Offload cross-cutting concerns via api gateway
• EDA between domains, with domain local data repos (non-normalised - more efficient for reads). Avoid cross-boundary violation
• Only go ms route if you have metrics that back up your supposition (don't use gut instinct)
• Trace cross-boundary requests for latency and failure rates - dashboards and alerts - must automatically assign to team/individual on the cover. - error management (e.g. sentry.io)
• Document as you go, must not be an afterthought
• No initial design will ever play out in reality so be flexible and adapt
• It's ok to change your mind - must have a culture that makes this ok and safe for everyone to do this - good engineering practices and leadership
• Monorepos for shared code - can still scale by deploying to separate docker containers
• Code to interfaces for client http calls to services. This avoids breaking changes and helps maintain code and deleting code that supports obsolete endpoints - often hidden by endpoints not being used. Recently spent several days moving dependency from one service to another to realise code wasn't even being used - versioning and code complexity was the culprit here. If not dealt with, this will absorb other engineer's time too.
• Keep code simple, doesn't need to be clever.
• Controllers (thin MVC) should be thin/light - biz logic in models

Include:

• security - HMAC
• function naming name.protected.js
• environments
• GH Actions, env vars and secrets