Should the first level of caching be included in the system architecture?

Including the first level of caching in the system architecture is advisable if:

• Access to data or computations is costly in terms of time or resources.
• There are frequently repeated requests for the same data.
• It is necessary to reduce the load on the database or external services.

The first level of cache is usually located closest to the application (for example, in the application's memory) and provides quick access to data. This improves system performance and responsiveness.

However, it is important to consider:

• Increased architectural complexity and the need for cache synchronization.
• The possibility of cache data becoming outdated.

If these risks are acceptable and the benefits of acceleration are significant, enabling the first level of caching is recommended.