Firestore Client in Google App Engine: Per-Request or Global?
Creating a Firestore Client in Google App Engine: Per Request or Global?
Context Awareness in Google App Engine
Google App Engine (GAE) suggests using a context.Context scoped to the HTTP request for each client library. This ensures that the client is tied to the specific request, providing context-specific data for the database operations.
Per-Request vs. Global Client
Per-Request Approach:
In the provided example, a new Firestore client is created within the handler function for each request:
func (s *server) person(ctx context.Context, id int) { _, err := s.db.Client.Collection("people").Doc(uid).Set(ctx, p) }
While this approach ensures the client is isolated to the current request, it can be inefficient and introduce unnecessary overhead, especially for long-running requests or high-frequency operations.
Global Client Approach:
An alternative approach is to create a single global Firestore client and reuse it for multiple requests. However, this was not feasible in the old Go runtime in GAE.
New Go 1.11 Runtime
With the introduction of the Go 1.11 runtime for GAE standard, the context scoping restrictions have been relaxed. This now allows you to use any context you prefer.
Best Practices for Go 1.11 and Firestore
In the new GAE standard runtime, it's recommended to:
-
Initialize the Firestore client in the main() or init() function using the background context:
func init() { var err error client, err = firestore.NewClient(context.Background()) }
Copy after login -
In request handlers, use the request context for API calls:
func handleRequest(w http.ResponseWriter, r *http.Request) { doc := client.Collection("cities").Doc("Mountain View") doc.Set(r.Context(), someData) }
Copy after login
By following these best practices, you can take advantage of the efficiency gains provided by reusing a global Firestore client while still maintaining request-specific context in your database operations.
The above is the detailed content of Firestore Client in Google App Engine: Per-Request or Global?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

This article introduces how to configure MongoDB on Debian system to achieve automatic expansion. The main steps include setting up the MongoDB replica set and disk space monitoring. 1. MongoDB installation First, make sure that MongoDB is installed on the Debian system. Install using the following command: sudoaptupdatesudoaptinstall-ymongodb-org 2. Configuring MongoDB replica set MongoDB replica set ensures high availability and data redundancy, which is the basis for achieving automatic capacity expansion. Start MongoDB service: sudosystemctlstartmongodsudosys
