7 Matching Annotations
  1. Apr 2020
    1. By using events that are buffered in queues, your system can support outage, scaling up and scaling down, and rolling upgrades without any special consideration. It’s normal mode of operation is “read from a queue”, and this doesn’t change in exceptional circumstances.

      Event driven architectures with replay / message logs

    2. Reserved resources, capacity, or physical hardware can be protected for pieces of your software, so that an outage in one part of your system doesn’t ripple down to another.

      Idea of Bulkheads

    3. The complimentary design pattern for all your circuit breakers – you need to make sure that you wrap all outbound connections in a retry policy, and a back-off.

      Idempotency and Retries design pattern

    4. Circuit breaking is a useful distributed system pattern where you model out-going connections as if they’re an electrical circuit. By measuring the success of calls over any given circuit, if calls start failing, you “blow the fuse”, queuing outbound requests rather than sending requests you know will fail.

      Circuit breaking - useful distributed system pattern. It's phenomenal way to make sure you don't fail when you know you might.

    5. Hexagonal architectures, also known as “the ports and adapters” pattern

      Hexagonal architectures - one of the better pieces of "real application architecture" advice.

      • have all your logic, business rules, domain specific stuff - exist in a form that isn't tied to your frameworks, your dependencies, your data storage, your message busses, your repositories, or your UI
      • all your logic is in files, modules or classes that are free from framework code, glue, or external data access
      • it means you can test everything in isolation, without your web framework or some broken API getting in the way
    6. all a design pattern is, is the answer to a problem that people solve so often, there’s an accepted way to solve it

      Design patterns are just bug fixes for your programming languages

      "they’re just the 1990s version of an accepted and popular stackoverflow answer"

    7. Let’s do a quick run through of some very common ones:

      most common design patterns:

      • MVC
      • ORM
      • Active Record
      • Repository
      • Decorator
      • Dependency Injection
      • Factory
      • Adapter
      • Command
      • Strategy
      • Singleton