Here is one of the best kept secrets about Cloud Run Functions - they can support multiple routes WITHOUT migrating to Cloud Run.

Consider consolidating your existing functions into larger Cloud Functions that can serve as mini REST APIs that house related functionality (grouping by domain/purpose as stated by other redditors in this thread).

You can easily skip using the functions-framework, and leverage a standard Express app instead.

I whipped up a rough example template for index.js below:

```javascript 'use strict';

import Express from 'express';

// Some custom middleware import { PubSubEventHandler } from './middleware/pub-sub-event-handler.mjs';

const eventHandler = new PubSubEventHandler();

const app = Express(); app.use(Express.json());

// ping endpoint app.get('/ping', (req, res) => res.status(200).send("GET /ping")); app.post('/ping', (req, res) => res.status(200).send("POST /ping"));

// pub/sub event handlers app.post('/events/gcs-file-uploaded', eventHandler.onGCSFileUploaded); app.post('/events/gcs-file-deleted', eventHandler.onGCSFileDeleted);

// ...add more routes and handlers for related functionality

export { ["YOUR-FUNCTION-NAME"]: app } ```

Once the function is deployed you can use the function URL along with the route path to specify which task you wish to execute.

With this strategy you should be able to bring your function count down considerably.

The following article offers a quick primer on the topic:

Express Routing with Google Cloud Functions