Based on the docs Neon has in GitHub, I have to disagree. The mechanisms are similar, esp how the Page Server keeps some pages cached locally, but they serve different goals. The Page Server cache and WAL consensus are both temporary storage.
In tiered storage databases individual tables or rows would move automatically and permanently between different mediums according to some criteria. eg: Latency sensitive data on nvme near the user, frequently accessed data stored on nvme and replicated globally, infrequently accessed data stored on spinning disks, etc.
In tiered storage databases individual tables or rows would move automatically and permanently between different mediums according to some criteria. eg: Latency sensitive data on nvme near the user, frequently accessed data stored on nvme and replicated globally, infrequently accessed data stored on spinning disks, etc.