DEV Community

Discussion on: Choosing Go when Building Lambdas

 
iseiryu profile image
Sergey

What is ISV?

I've been using AWS lambdas long enough to know the difference between hosting my apps on classic managed and self-managed VMs as well as containers and serverless.

Serverless is great for small things, for automation, it could be a good option for internal tools. It can also be a good option when you do not expect a lot of traffic and your budget is very tight.

It's pretty bad when it comes to building bulletproof public facing real time apps (in comparison to other forms of hosting and development). It's possible, but other options allow you to develop and troubleshoot things simpler and faster.

Thread Thread
 
benbpyle profile image
Benjamen Pyle

ISV = Independent Software Vendor.

I'm glad to have different opinions on this topic. I've been successfully building large Serverless Apps for a while now and couldn't be happier. I don't consider Lambda == Serverless so that umbrella to me includes things like SQS, SNS, Kinesis, DDB, EventBridge etc. Lambda is just a piece.

If I wanted < 5ms latency consistently, it's not my goto for things like that. So sure, a container and gRPC or another mechanism for communicating makes more sense. I might not even choose something Event-Driven in that case.

Simpler and faster ... again just opinions. Love the dialogue though and thanks for weighing in :)