A Spanner instance defines an infrastructure configuration and compute capacity for its databases. The database then has its own identity and dialect. Elm Ledger needs to review those choices without treating the instance name as a SQL engine result.
Choose one capacity unit for the command: nodes or processing units. A small supplied training allocation is not a production recommendation, and a regional configuration name does not establish the application's achieved availability. The local adapter records the instance, then a database under the selected parent. It does not execute queries, distribute transactions, provision replicas, or measure throughput. You will practice both capacity forms and a database creation with an explicit dialect. The decision tasks keep parent scope, data correctness and workload validation separate from the success of a resource declaration.
Read capacity units and database parent scope independently.