How to mix and match serverless and serverful components

[@googlecloudtech]

Have you run into any problems when mixing serverless and serverful components? Let Martin know in the comments below!

[@guillaumeblaquiere]

Cloud task is great for async use case, like pubsub. For sync use case, max instance is the key!

[@konigdermasai]

I'd say better to use Cloud Pub/Sub than Cloud Tasks in these use cases. Cloud Tasks its just for a serverless task queue, but Pub/Sub can connect asynchronously any app in a decoupled way. Tasks can set task rate at the task queue, but you can better control rate from the subscribers using Pub/Sub

[@TheMomander]

Pub/Sub is also a great choice. For anyone thinking about these two products, I recommend doing a search for "cloud tasks vs pubsub" and you will see a Google-authored page comparing and contrasting the two.

[@TheOnlyEpsilonAlpha]

Cloud Tasks as a buffer 🤔 interesting

[@saisrihari3992]

What is meant by server less and server full

[@TheMomander]

Good question! "Serverless" is when you don't need to allocate resources (like virtual machines) up-front, but you only pay for how much you use. And if your use is zero, you pay zero. Google Cloud Run is an example if a serverless platform. "Serverful" is when you need to allocate resources ahead of time, like a virtual machine. You'll pay for that virtual machine regardless of whether it runs your code or not. Google Compute Engine is an example of a serverful platform.

[@dailymeow3283]

I havn't 😅 i don't have that much traffics

[@NurilGamer999]

Plot twist: "serverless" is not serverless

[@TheMomander]

Agreed -- "serverless" is a misleading term. Unfortunately we are stuck with it. I invite you to do a KZbin search for "you came up with a new word for serverless" and you will see a video where I go through words that people suggested we should use instead. Some of the suggestions were great!