25 Matching Annotations
  1. Apr 2021
  2. Mar 2021
    1. I originally said: It feels like the principle of least power in action. But another way of rephrasing “least power” is “most availability.” Technologies that are old, simple, and boring tend to be more widely available.

      This is also the reason that space platforms are built on incredibly old computing systems, we know what all the problems and issues are. Then when the satellite is up in outer-space where it's not accessible and not easily repairable, it will hopefully work as expected forever.

  3. Feb 2021
  4. Oct 2020
  5. Sep 2020
    1. the availability heuristic. The easier it is to access, the more relevant we think it is.

    Tags

    Annotators

  6. Aug 2020
  7. Jul 2020
    1. The most controversial crime-related posts get the most engagement. In turn, these posts are featured the most in users’ notifications because the algorithm knows those posts attract lots of likes, comments, and clicks.

      I wonder if this also increases the availability heuristic implicit and makes people think there is more crime in their neighborhood than there actually is?

  8. Jun 2020
  9. May 2020
  10. Jun 2017
    1. no data loss will occur as long as producers and consumers handle this possibility and retry appropriately.

      Retries should be built into the consumer and producer code. If leader for the partition fails, you will see a LeaderNotAvailable Exception.

    2. By electing a new leader as soon as possible messages may be dropped but we will minimized downtime as any new machine can be leader.

      two scenarios to get the leader back: 1.) Wait to bring the master back online. 2.) Or elect the first node that comes back up. But in this scenario if that replica partition was a bit behind the master then the time from when this replica went down to when the master went down. All that data is Lost.

      SO there is a trade off between availability and consistency. (Durability)

    3. keep in mind that these guarantees hold as long as you are producing to one partition and consuming from one partition.

      This is very important a 1-to-1 mapping between writer and reader with partition. If you have more producers per partition or more consumers per partition your consistency is going to go haywire