From reading it, I'm not really sure if it's eventually consistent or not. > Replicas then update cache pages in the shared buffers. This ensures eventual cons

From reading it, I'm not really sure if it's eventually consistent or not. > Replicas then update cache pages in the shared buffers. This ensures eventual consistency for read replicas within the same region as your database. > Data Consistency: Reading data from a single source ensures data consistency. This addresses a common challenge in traditional read replicas where there might be a replication lag. > Resource Customization: Neon allows you to allocate different CPU and memory resources for each replica. So there is a single source of data, but can have different CPU and memory and has eventual consistency in the same region?