amazon web services - What's the best server solution to handle high traffic? -
the requirement
there should web service inserts data table. service should able handle 800 900 requests per second. post request insert data in table.
the solution came up
we thought of go amazon serverless solutions - aws lambda
- create mariadb in amazon rds
- create amazon lambda function access db , insert data (probably in node.js)
- configure post method in amazon api gateway access our lambda function, invoke url access lambda function
can our solution achieve requirements, bottlenecks in process or services use??
is there better solutions handle kind of traffic?
additional requirements
we need analyze our data collect through our lambda function. planning move data different table , data migration part happens once day (probably during off-peak). what's best way handle data migration?
it appears design api gateway -> lambda -> database.
amazon api gateway highly scalable , meet needs easily. implement throttling rules make sure clients not abusing api.
aws lambda highly scalable. there default limit of 1000 concurrent lambda function executions, automatically queue if amount exceeded (eg if function takes several seconds complete).
in general, sql databases have no guarantee of performance. query can simple or complex , hard predict performance without running lots of load tests.
however, amazon dynamodb nosql database can configure how many reads , writes per second require. allows limited burst above limit , ability auto scale vary performance throughout day.
the downside is difficult performance analysis on data in nosql database, want export either traditional sql database (eg mysql) or elk stack on amazon elasticsearch service.
Comments
Post a Comment