Week 2023-W27 in reading

Sources:

1. Reactive Manifesto
2. Reactive Principles

Key properties of a Reactive system:

• responsive — responds in a reasonable time if possible;
• resilient — stays responsive even when failures occur (e.g. fail gently, isolate failures so they don't propagate and cause the whole system to fail);
• elastic — stays responsive under varying load;
• message-driven — relies on asynchronous communication.

My key take-away here is that asynchronously processed messages update some model behind the scenes, so when the time comes to return some data to the user, it is ready. However, this probably involves eventual consistency and increased complexity.

See also:

• Martin Fowler's "Event Sourcing"
• Bulkhead pattern

Source: Evolving HTTP APIs

1. Compatible versions shouldn't cause any adjustments (shouldn't change versions).
2. Avoid major / incompatible versions.
3. Be backward-compatible, but still limiting the impact. New version requires everyone to adapt, so keeping the same version with some adjustments might make more sense from effort perspective.

Sources:

1. Self-contained Systems: A Different Approach to Microservices
2. Self-Contained Systems

This idea doesn't sound very innovative, while it does sound a bit strict. Experience tells me being strict is good in theory, while practice one has to be flexible/open and mix things to achieve goals.

According to release notes:

Certain Firefox users may come across a message in the extensions panel indicating that their add-ons are not allowed on the site currently open. We have introduced a new back-end feature to only allow some extensions monitored by Mozilla to run on specific websites for various reasons, including security concerns.

However, this isn't very transparent about those other reasons for blocking extensions. Could for example Google request Mozilla to disable ad-blockers on YouTube?