Lagom: Support integration with GCP Pub/Sub using the Message Broker API

[idoshamun]

https://cloud.google.com/pubsub/docs/overview

Google Cloud Pub/Sub brings the scalability, flexibility, and reliability of enterprise message-oriented middleware to the cloud. By providing many-to-many, asynchronous messaging that decouples senders and receivers, it allows for secure and highly available communication between independently written applications. Google Cloud Pub/Sub delivers low-latency, durable messaging that helps developers quickly integrate systems hosted on the Google Cloud Platform and externally.

For me and I guess many other GCP users, it makes more sense to use a managed solution such as Pub/Sub than deploying a Kafka cluster.

Related: https://developer.lightbend.com/docs/alpakka/current/google-cloud-pub-sub.html

[octonato]

This is a great idea!

I would prefer to have it as a separated module. By that I mean, Lagom should offer a broker API, like it's doing now, and we should be able to provide different implementations. And those implementations should preferably be on a separated project and supported by the community.

Would you be up for working out a prototype? While working on it, we may identify things we must add to the broker API to make it possible. WDYT?

[idoshamun]

I am up to the challenge but I think I will need guidance as I am currently doing my first steps in Lagom, though experienced with Scala & Akka

[idoshamun]

A WIP repo of the implementation:
https://github.com/elegantmonkeys/lagom-google-pubsub

Not yet tested, looking for reviewers and testers

[idoshamun]

@renatocaval @TimMoore my first kind of stable version is ready, the only thing missing is atMostOnceSource which currently not supported by Pub/Sub.
I am now integrating this library to one of our projects.
How would you like to proceed with this library?

[ignasi35]

Hi @idoshamun this looks great. I think it's best if you could release the library's components (javadsl and scaladsl) into maven central for 3rd parties to use. I would move the discussion to the elegantmonkeys repo too.

[idoshamun]

@ignasi35 totally right! I will do my best publishing everything as soon as possible and we will continue the discussion in the repo.