Merge pull request #13 from dferber90/patch-1

move edgeConfigClient outside of handler

README.md

@@ -28,6 +28,10 @@ The project overall architecture is ilustrated in the following diagram:
     // Deploying as an Edge function here, but you can also use it on Edge middlewares and Serverless functions
     export const config = { runtime: "edge" };
 
+    // Creates a client which knows how to read from Edge Config
+    // This client is defined outside of the handler so that it can be reused across requests
+    const edgeConfigClient = createClient(process.env.EDGE_CONFIG);
+
     export default async function handler(req, event) {
       // Extract user key. In this case from a request query param
       const { searchParams } = new URL(req.url);
@@ -45,7 +49,7 @@ The project overall architecture is ilustrated in the following diagram:
             edgeConfigItemKey: '<YOUR_EDGE_CONFIG_ITEM_KEY>',
             // The Edge Config client. In this case, we are passing the default client
             // that reads from the Edge Config stored in process.env.EDGE_CONFIG
-            edgeConfig: createClient(process.env.EDGE_CONFIG)
+            edgeConfig: edgeConfigClient,
           })
         }),
         // Disable or keep only ERROR log level in production, to minimize performance impact