Readings: AWS: Events
Review, Research, and Discussion
- Describe the similarities between AWS API Gateway + Lambda functions and an ExpressJS Server ?
- They will handle http request endpoints.
- List the AWS Database offerings and talk about the pros and cons of each
- Amazon RDS
- Amazon Relational Database Service or Amazon RDS is a managed cloud database service from AWS. It is a service designed to simplify the creation, operation, management, and scaling of a relational database for use as an application backend. AWS launched the RDS service initially in October 2009 with support for MySQL.
- Amazon RDS
| Pros | Cons |
|---|---|
| Automated Patching | Patching forces a downtime |
| Automated Backups | No scale-out for write workloads |
| Encryption at rest and in-transit | Downtime required for scaling operations |
| Significant improvement over on-premise databases | No automated performance tuning |
| Integrated with rest of the AWS ecosystem | Not a zero-administration database |
| No hardware maintenance needed | No automated partition management |
| Simplified scaling in comparison to on-premise databases | No automated compression management |
| Automated log shipping and read read replica | No root access to the server |
| Simplified disaster recovery and automatic failover | No native support as a read replica for on-premise Databases |
| Automated additional storage allocation | CPU and Storage performance is not guaranteed |
| Point in time recovery | Zero data loss is not guaranteed |
-
For further information clicks =>here
- What’s the difference between a FIFO and a standard queue?
- Standard queues guarantee that a message is delivered at least once and duplicates can be introduced into the queue.
-
FIFO queues ensure a message is delivered exactly once and remains available until a consumer processes and deletes it; duplicates are not introduced into the queue.
-
For further information clicks =>here
- How can the server be assured a message was properly received?
-
The message oriented architecture is a solution where nodes communicate by sending messages. The key factor in this approach is an ability to communicate in an asynchronous way. This kind of information exchange gives wide possibilities to manage both time and delivery path. When a traditional synchronous model takes place, client has to wait being blocked until server replies or a timeout mechanism occurs (if applicable).
-
For further information clicks =>here
-
Vocabulary
- Serverless API
- Serverless is a cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. A serverless application runs in stateless compute containers that are event-triggered, ephemeral (may last for one invocation), and fully managed by the cloud provider.
-
For further information clicks =>here
- DynamoDB vs MongoDB
| DynamoDB | MongoDB |
| ———– | ———– |
| MongoDB is vendor agnostic, Open Source, and can be deployed anywhere | DynamoDB is only available on AWS |
| MongoDB can be self installed or fully managed with MongoDB Atlas | DynamoDB is a fully managed AWS service |
| DynamoDB uses tables, items and attributes | MongoDB uses JSON-like documents |
| DynamoDB supports limited data types and smaller item sizes | MongoDB supports more data types and has fewer size restrictions |
-
For further information clicks =>here
-
- Dynamoose vs Mongoose
- Dynamoose used by the AWS, Mongoose used by the Express
-
For further information clicks =>here
Preparation
- SQS and SNS Basics
- SNS is a distributed publish-subscribe system. Messages are pushed to subscribers as and when they are sent by publishers to SNS.
-
SQS is distributed queuing system. Messages are not pushed to receivers. Receivers have to poll or pull messages from SQS.
-
The Amazon Simple Queue Service (SQS) and the Amazon Simple Notification Service (SNS) are important “glue” components for scalable, cloud-based applications (see the Reference Architectures in the AWS Architecture Center to learn more about how to put them to use in your own applications).
| Read | Title | ToGo |
|---|---|---|
| Read: 01 | Pre-Work - Code 401: Advanced Javascript Development |  |
| Read: 02 | Readings: Express | |
| Read: 03 | Readings: Express REST API | |
| Read: 04 | Readings: Data Modeling | |
| Read: 06 | Readings: Authentication | |
| Read: 07 | Reading: Bearer Authorization | |
| Read: 08 | Reading: Access Control (ACL) | |
| Read: 09 | Reading: OAuth 2 | |
| Read: 11 | Readings: Event Driven Applications | |
| Read: 12 | Readings: Socket.io | |
| Read: 13 | Readings: Message Queues | |
| Read: 14 | Readings: Event Driven Architecture | |
| Read: 16 | Readings: AWS: Cloud Servers | |
| Read: 17 | Readings: AWS: S3 and Lambda | |
| Read: 18 | Readings: AWS: API, Dynamo and Lambda | |
| Read: 18 | Readings: AWS: Events | |
| Read: 26 | Reading: Component Based UI | |
| Read: 27 | Reading: Props and State | |
| Read: 28 | Readings: Component Composition | |
| Read: 29 | Readings: Routing | |
| Read: 31 | Reading: Hooks API | |
| Read: 32 | Reading: Custom Hooks | |
| Read: 33 | Reading: Context API | |
| Read: 34 | Reading: <Login /> and <Auth /> |
|
| Read: 36 | Reading: Application State with Redux | |
| Read: 37 | Readings: Redux - Combined Reducers | |
| Read: 38 | Readings: Redux - Asynchronous Actions | |
| Read: 39 | Readings: Redux - Additional Topics | |