Hi everyone,
I'm working on improving how we handle short-notice customer requests inside a cloud-based workflow. In our case, customers often reach out very close to their required service time, so we need a fast way to capture the request, validate details, and route it to the right team without delays.

I'm exploring different patterns using IBM Cloud resources and wanted to get some input from the community on:

• Whether IBM Cloud Functions is suitable for handling sudden spikes in small, fast tasks

• Best practices for building a lightweight request flow that keeps latency low on mobile devices

• Techniques to avoid shared-state issues when multiple requests hit the system at once

• Using App Connect vs. Event Streams for routing these short-notice events

• General architecture patterns you've found useful for real-time or near-real-time customer interactions

I'd love to hear any suggestions or examples from people who've solved similar problems.
Thanks in advance!

------------------------------
Sergio
Toronto Pearson Airport Taxi
Toronto ON
647 927-9321
------------------------------

IBM Cloud Functions is great for short, spiky tasks-its serverless model auto-scales to handle sudden request surges. For mobile latency, pair it with Cloudant for lightweight data storage to cut round-trips. Also, Event Streams is more robust than App Connect for real-time routing of these urgent requests.

------------------------------
djj d
------------------------------

Original Message:
Sent: Sat December 06, 2025 03:54 AM
From: Sergio
Subject: Best approach for managing short-notice customer requests in a cloud-based workflow?

Hi everyone,
I'm working on improving how we handle short-notice customer requests inside a cloud-based workflow. In our case, customers often reach out very close to their required service time, so we need a fast way to capture the request, validate details, and route it to the right team without delays.

I'm exploring different patterns using IBM Cloud resources and wanted to get some input from the community on:

• Whether IBM Cloud Functions is suitable for handling sudden spikes in small, fast tasks

• Best practices for building a lightweight request flow that keeps latency low on mobile devices

• Techniques to avoid shared-state issues when multiple requests hit the system at once

• Using App Connect vs. Event Streams for routing these short-notice events

• General architecture patterns you've found useful for real-time or near-real-time customer interactions

I'd love to hear any suggestions or examples from people who've solved similar problems.
Thanks in advance!

------------------------------
Sergio
Toronto Pearson Airport Taxi
Toronto ON
647 927-9321
------------------------------