Application Services Flashcards
What type of service has no instances to manage?
Serverless Services:
With Serverless technology there are no instances to manage
- You do not need to provision hardware
- There is no management of operating systems or software
- Capacity provisioning and patching is handled automatically
- Provides automatic scaling and high availability
Examples of Serverless Servers
Examples of Serverless Services: -AWS Lambda ---->Compute Service AWS Fargate ---->Docker Containers -Amazon EventBridge -AWS Step Functions -Amazon SQS, Amazon SNS -Amazon API Gateway -Amazon S3 -Amazon DynamoDB
A fully managed NoSQL database service that provides fast and predictable performance with seamless scalability:
Amazon S3
Amazon Elasticache
Amazon DynamoDB
Amazon CloudFormation
Amazon DynamoDB
A fully managed NoSQL database service that provides fast and predictable performance with seamless scalability
Database tables that can store and retrieve any amount of data and serve any level of request traffic.
Provides on-demand backup capability
Serverless service that enables us to run code in response to triggers:
AWS Lambda
AWS Fargate
AWS DynamoDB
AWS API Gateway
AWS Lambda Functions:
Serverless service that enables us to run code in response to triggers
—->similar to WAS service or Host fetchable
Developer places their code into a Lamda function
—->Receives an ‘event’ and processes the code
- Processed file could be :
- —>Stored in a S3 bucket
- —>Sent to a queue
- —>Stored in a dateabase (DynamoDB Table)
- —>Sends notification using SNS Topic that goes out to an email address
- Triggering event could be:
- —>CLI
- —>API
- —>SDK
- —>Trigger (scheduled event)
Executes code only when needed and scales automatically
Pay only for the compute time you consume (you pay nothing when code is not running)
Benefits:
- No instances to manage
- No hardware to provision, no management of OPS or software
- Continuous automatic scaling
- Millisecond billing
- Integrates with almost all other AWS services
- High availability
- VERY cheap
Primary use:
- Data processing
- Real-time file processing
- Real-time stream processing
- Build serverless backends for web, mobile, IOT and 3rd party API requests
A serverless service used for running Docker Containers in the cloud:
AWS Lambda
AWS Fargate
AWS DynamoDB
AWS API Gateway
Fargate
Elastic Container Service (ECS) launch type
AWS manages the underlying computer, cluster, and scaling
Automatically provisions and manages and scales the underlying resources
Only pay for the tasks themselves
You do NOT have to manage underlying infrastructure
Offers a reliable, highly-scalable, hosted queue for storing messages in transit between computers and is used for distributed/decoupled applications:
Amazon MQ
Amazon Lamda
Amazon Simple Queue Service (SQS)
Amazon Simple Notification Service (SNS)
Amazon Simple Queue Service (SQS)
- Offers a reliable, highly-scalable, hosted queue for storing messages in transit between computers
- Used for distributed/decoupled applications
- Uses a message-oriented API
Uses pull based (polling/not push based)
Example: Web sends message through but is held in a SQS Queue and our application will call/poll the queue and retrieve the messages as it is able. So things don’t get ‘jammed up’ if a large influx of messages starts coming through.
Message broker service used when customers require industry standard API’s and protocols:
Amazon MQ
Amazon Lamda
Amazon Simple Queue Service (SQS)
Amazon Simple Notification Service (SNS)
Amazon MQ
- Message broker service
- Similar to Amazon SQS BUT based on Apache Active MQ and RabbitMQ (not AWS)
- Used when customers require industry standard API’s and protocols
- Useful to migrate existing queue-based applications into the cloud
Publisher/subscriber model used for building and integrating loosely-coupled, distributed applications to send communications:
Amazon MQ
Amazon Lamda
Amazon Simple Queue Service (SQS)
Amazon Simple Notification Service (SNS)
Amazon Simple Notification Service (SNS):
Sends notifications
Publisher/subscriber model (Publisher sends a message to Amazon Simple Notification Service and that is pushed to a subscriber)
Publisher = Amazon EC2, Amazon CloudWatch or Amazon S3 (Simple Storage Service)
Subscriber = Amazon Simple Queue Service, SMS/Email or AWS Lamda
Used for building and integrating loosely-coupled, distributed applications
Provides instantaneous, push-based delivery (no polling)
Uses simple API’s and easy integration with applications
Offered under an inexpensive, pay-as-you-go model with no up-front costs
Allows application to be configured to send a notification to multiple amazon SQS queues:
Amazon Gateway
Amazon Shield
SNS Topic
Access Keys
SNS Topic
Allows application to be configured to send a notification to multiple amazon SQS queues
Makes it easy to coordinate the components of distributed applications as a series of steps in a visual workflow
Can quickly build and run state machines to execute the steps of your application in a reliable and scalable fashion
AWS Step Functions
Similar to BPM
- Coordinate work across distributed application components
- Create distributed asynchronous systems as workflows
- Best suited for human-enabled workflows like an order fulfilment system or for procedural requests:
AWS Step Functions
Amazon EventBridge
Event Driven Application
Amazon Simple Workflow Service (SWF)
Amazon Simple Workflow Service (SWF)
Coordinate work across distributed application components
Create distributed asynchronous systems as workflows
Best suited for human-enabled workflows like an order fulfilment system or for procedural requests.
Serverless event bus formerly known as CloudWatch Events used for building event-driven architectures:
AWS Step Functions
Amazon EventBridge
Event Driven Application
Amazon Simple Workflow Service (SWF)
Amazon EventBridge
New name for CloudWatch Events
Serverless event bus
Used for building event-driven architectures
Ingests data and routes it to target AWS services
Example:
EC2 instance unexpectedly terminates—–>EventBridge is called to alert of the termination—> EventBridge calls a rule which directs it to send a SNS notification
An event in one resource leads to an event in another resource:
AWS Step Functions
Amazon EventBridge
Event Driven Application
Amazon Simple Workflow Service (SWF)
Event Driven Application
Where an event in one resource leads to an event in another resource
Example:
User submits notification to SNS Topic–>Amazon SNS Topic sends event to Amazon SQS–>SQS triggers a Lamda target–> Lamda writes an event into CloudWatch logs (that event should match the original notification from the user)
