in our serverless application(s) we still use types, and yes, that requires runtime verification at more boundaries, and therefore technically more compute cycles. we share those types across all our Lambdas. Yes, technically each Lambda must be deployed separately; in our case any changes to message-passing types would require equivalent "overhead" as a no-downtime database migration - then again, the best practice here is the same as with databases - always try to make your types backwards-compatible, only adding new fields, etc.
there's certainly _a_ cost; I just haven't seen it be as high as people seem to imagine.
there's certainly _a_ cost; I just haven't seen it be as high as people seem to imagine.