Inferesting read and I've been waiting for a review of serverless.com I had a choice with my own product to go FaaS or lump together some into "larger" microservices (mainly to reduce chatter across networks). In the end deploying containers ended up being the route but, definitely would like to dig into serverless functions, it makes a lot of sense.
You eluded to this, but do you think there will be a mix of functions and larger services in containers as more of a microservice rather than lambdas to increase performance (reduce the cold starts and network overheads)
How have you found supporting this setup? Especially when it comes to monitoring, alerting and permissions between services. Does the framework handle that for you?
To answer your first question: Yes, we expect a mix of services in containers and services in Lambda functions. We are beginning to use Fargate with ECS to improve performance.
Regarding your second question, Serverless Framework has gotten us through the product early stages, but as we're scaling and growing we've needed to do a lot more load and performance testing and, as a result, we're enhancing our architecture to take advantage of AWS services like Fargate that can get us to that next level of growth and performance.
As for monitoring and alerting, we'll considering doing a future post about DataDog integration as this is a big topic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Inferesting read and I've been waiting for a review of serverless.com I had a choice with my own product to go FaaS or lump together some into "larger" microservices (mainly to reduce chatter across networks). In the end deploying containers ended up being the route but, definitely would like to dig into serverless functions, it makes a lot of sense.
You eluded to this, but do you think there will be a mix of functions and larger services in containers as more of a microservice rather than lambdas to increase performance (reduce the cold starts and network overheads)
How have you found supporting this setup? Especially when it comes to monitoring, alerting and permissions between services. Does the framework handle that for you?
Thanks for sharing!
To answer your first question: Yes, we expect a mix of services in containers and services in Lambda functions. We are beginning to use Fargate with ECS to improve performance.
Regarding your second question, Serverless Framework has gotten us through the product early stages, but as we're scaling and growing we've needed to do a lot more load and performance testing and, as a result, we're enhancing our architecture to take advantage of AWS services like Fargate that can get us to that next level of growth and performance.
As for monitoring and alerting, we'll considering doing a future post about DataDog integration as this is a big topic.