Please enable JavaScript.
Coggle requires JavaScript to display documents.
Serverless, DynoDB, API Gateway, Cognito, Lambda, Serverless Application…
-
DynoDB
Advanced features
DAX
Seamless cache, no rewrite, got for hot key problem of millions of requests
-
On-Demand
No limit on throughput for RCU/WCU, more expensive but good for unpredictable applciations or low throughput applications
Global tables
Application replication to multiple regions, must enable for DynoDB, good for low latency
Definition
-
Millions of requests, scales to massive workloads, low latency
-
-
DynoStreams
Event driven programming
-
-
RCU throughput(1 strongly consistent of 4kb per second), 2 eventually consistent
WCU throughput ; 1 write of 1 kb per second
IF RCU is exceeded, Burst credits, if empty you get a provisioned throughput exception
API Gateway
Endpoints
Edge-optimized
For global clients, located in one region
Regional
For clients within the same region, more control over caching policies
Private
Can be accessed from your VPC using interface endpoint, AWS resource must allow access
Security
IAM: Authentication + authorization, Sigv4 capability where IAM credentials are in the header
LAmbda/Custom: Use lambda header to verify tokens, good for 3rd party, authentication +authorization
-
-
Cognito
Cognito Sync
Required Federated Identity, stores configuration state of the app, offline capability and cross device synchronization
-
A serverless database for of the user for your mobile apps, simple log-in, can enable Federated IDentities, and be integrated with the API gateway
Lambda
-
Limits
3 gb deployment, short execution times, 4kb environment, 50 mb deployment
-
