Skip to main content

FiftyFive Tech

Email Us sales@fiftyfivetech.io
Get in Touch
Close-up of two hands working the knobs, faders and glowing pads of a dark music controller

Generative AI applications

Low-latency conversational assistant back end on Google Cloud

FiftyFive developed a Google Cloud back end for a personalised conversational assistant, using Gemini, Cloud Run, Pub/Sub, Firebase and Terraform.

Discuss your conversational AI back end
Industry
Media & Entertainment — music
Region
Europe
Solution
Google Cloud conversational AI back end
Story

About the client

The client is a music artist interested in applying AI to creative work. The goal was a conversational assistant that fans could talk to through text and audio, with responses personalised to the artist's way of speaking. What began as an experiment grew into a need for a back end that could handle real-time conversations reliably as usage grew.

Challenge

Real-time, personalised conversation at low latency

  • Text and audio. Convert text and audio inputs into structured data while preserving context and intent.
  • High-frequency queries. Handle high-frequency queries at low latency.
  • Consistent transactions. Keep transactions consistent in Firebase Realtime Database.
  • Phonetic data. Retrieve and format phonetic data efficiently.
  • Secured deployment. Deploy securely and scalably with infrastructure as code.
  • Tuned responses. Tune Gemini API responses so they are personalised and context-aware.
Solution

What FiftyFive built

FiftyFive developed a full back-end pipeline: a modular back end on Google Cloud Run; asynchronous messaging with Pub/Sub for high-frequency queries; real-time data synchronisation with Firebase Realtime Database; a Flask service layer managing service interactions and data routing; integration of Google Gemini API responses with a third-party phonetic API; automated, repeatable deployment with Terraform.

How the solution works

  1. Input handling

    • Text and audio inputs are converted into structured data that keeps the user's context and intent, so the rest of the pipeline works with a consistent format.
  2. Asynchronous processing

    • Queries are passed through Pub/Sub, decoupling incoming requests from processing.
    • Bursts of high-frequency queries queue rather than overwhelm the services, which run on Cloud Run and scale with demand.
  3. Response generation

    • A Flask service layer routes each request.
    • Responses come from the Google Gemini API, tuned for personalised, context-aware replies, and are combined with phonetic data retrieved from a third-party phonetic API.
  4. State and deployment

    • Firebase Realtime Database keeps conversation data in sync in real time, with attention to transaction integrity.
    • The whole stack is deployed with Terraform, so environments are reproducible and secured consistently.

Technology stack

Google Gemini APIPersonalised, context-aware response generation
Google Cloud RunHosting for the modular back-end services
Google Cloud Pub/SubAsynchronous handling of high-frequency queries
Firebase Realtime DatabaseReal-time data synchronisation
FlaskService interactions and data routing
Third-party phonetic APIPhonetic data combined with generated responses
TerraformAutomated, reproducible infrastructure deployment

What the solution enabled

Outcomes

Business transformation

Low latency

Real-time conversational queries on Google Cloud

2 inputs

Text and audio converted into structured data

Terraform

Automated, repeatable deployment

Low-latency pipeline

Modular back-end pipeline for real-time conversational queries on Google Cloud.

Personalised replies

Integration of Gemini-generated responses with phonetic metadata.

Pub/Sub and Firebase

Asynchronous processing, with real-time state.

Infrastructure as code

With Terraform, giving the client a base for further development.

FiftyFive Technologies developed the back end for a personalised conversational assistant for a European music artist who wanted fans to interact with an assistant reflecting the artist's speech patterns. The modular pipeline runs on Google Cloud Run, uses Pub/Sub for asynchronous handling of high-frequency queries, Firebase Realtime Database for real-time data sync and a Flask service layer, and combines Google Gemini API responses with phonetic data from a third-party API. Terraform automates deployment.

FAQ

Technical questions

How does the conversational assistant handle high-frequency queries?

Queries are passed through Pub/Sub, decoupling incoming requests from processing. Bursts of high-frequency queries queue rather than overwhelm the services, which run on Cloud Run and scale with demand.

How are the responses personalised?

A Flask service layer routes each request. Responses come from the Google Gemini API, tuned for personalised, context-aware replies, and are combined with phonetic data retrieved from a third-party phonetic API.

Discuss your conversational AI back end with FiftyFive's engineers.

Book a call

Project snapshot

Industry
Media & Entertainment — music
Region
Europe
Services
Back-end development, AI integration, cloud engineering, infrastructure automation
Core technologies
Google Gemini API, Cloud Run, Pub/Sub, Firebase Realtime Database, Flask, Terraform