DEV Community

Gracie Gregory (she/her) for The DEV Team

Posted on

We want to feature your voice on DevDiscuss! This week's topic: serverless and the cloud.

The DevDiscuss Podcast begins with an interview and ends with commentary from listeners β€” and we like to feature the actual voices from our community!

For your chance to appear on an upcoming episode:

  • Call our Google Voice at +1 (929)500-1513 and leave a message πŸ“ž

  • Send a voice memo to pod@dev.to πŸŽ™

  • Or, leave a comment here and we'll read your response aloud for you πŸ—£

Please send in your recordings by August 26 at 5 PM PT (8 PM ET, 12 AM UTC)

This week's prompt: "What do you wish you knew about serverless and the cloud?"


Don't forget to check out the latest episode, released on Wednesday!

Discussion (10)

Collapse
somedood profile image
Basti Ortiz

The pricing model for various Cloud services have always confused me. The "pay-for-what-you-use" model is often ambiguously worded with terms like "microcents per minute" and whatnot.

What does it mean to charge "per minute"? Does it take into account the total time a service is idle? Or does it take into account the total time it took to process all requests within a month? Or perhaps the price reflects the total uptime of the service itself within a month?

It would be great to clear up these ambiguities in the computation of "processing minutes", especially when there are some gotchas involved.

Collapse
graciegregory profile image
Gracie Gregory (she/her) Author

Hey @somedood ! If you're interested, we'd love to get a voice recording of this comment (or a similar one) to feature in a future episode! If you're interested in hearing your voice on the podcast, instructions for submitting a Google voice recording are above :)

Collapse
zilti profile image
Daniel Ziltener

It is just a scheme to rip you off and charge you ridiculous sums.

Collapse
meseta profile image
Yuan Gao

I have a more of a "what I'm glad I know": we encountered several use cases where we could really benefit from serverless, but we needed some fairly big binaries to be installed as part of the runtime. public cloud offerings didn't give us enough flexibility to do it, so we turned to our own installation of Kubeless as a sort of "roll your own cloud functions". that turned out great - we could roll our own runtime images which contain all the dependencies we need, and the serverless deployment was painless for developers.

It's lead me to realize that this could be representative of the future of serverless - where some organizations that can benefit from rolling their own serverless stack as part of an internal platform; and expanding the DevOps function to take a bigger role in maintaining these internal platform services, letting developers focus on business logic rather than infrastructure, which is exactly the benefit of serverless on the public cloud right now for those with simpler requirements.

Collapse
kyleboe profile image
Kyle Boe

This isn't specifically my area of expertise, but you should hit up my coworkers Joel and Nate. They just got done writing about their heaps of serverless experience using Ruby and AWS Lambda to reduce process times by 300x.

Collapse
stereoplegic profile image
Mike Bybee • Edited on

Better Authentication as a Service documentation for integrating with third party serverless, from providers not named Auth0 (looking at you, Firebase Auth, or AWS when not using Cognito/"Amplify Auth" directly/exclusively, or FaunaDB, or...).

Collapse
jerielng profile image
Jeriel Ng

What would a personal project in serverless/cloud computing look like? Since there's always a pricing model for these service platforms, how do you effectively learn these tools without incurring massive costs?

Collapse
rolfstreefkerk profile image
Rolf Streefkerk

hint, look at AWS Free Tier, you'll notice that many of those serverless Services won't cost you a dime ;)

Collapse
bernardbaker profile image
Bernard Baker

Looking forward to this episode 😍