presention slide on AWS lamda.

1. AWS SERVILANCE LAMDA
SUBMITTED BY- MOHIT MALVIYA
MCA 6TH SEM
SEMINAR ON LATEST TOPIC
Design By- Mohit Malviya

2. Micro
Services
Design By- Mohit Malviya

3. #1 Componentization via Services
Design By- Mohit Malviya

4. #2 Organized around Business Capabilities
Design By- Mohit Malviya

5. #3 Products not Projects
Design By- Mohit Malviya

6. #4 Smart endpoints and dumb pipes
Design By- Mohit Malviya

7. #5 Decentralization
Design By- Mohit Malviya

8. #6 Infrastructure Automation
Design By- Mohit Malviya

9. #7 Design for failure
Design By- Mohit Malviya

10. #8 Evolutionary Design
Design By- Mohit Malviya

11. Using Amazon CloudWatch
• AWS Lambda automatically monitors Lambda functions on your
behalf, reporting metrics through Amazon Cloud Watch. To help you
monitor your code as it executes, Lambda automatically tracks the
number of requests, the latency per request, and the number of
requests resulting in an error and publishes the associated Cloud
Watch metrics. You can leverage these metrics to set Cloud Watch
custom alarms.
Design By- Mohit Malviya

12. Tools to Create and Test
Lambda-based Applications
• There are three key tools that you use to interact with the AWS Lambda service,
described below. We will cover tools for building AWS Lambda-based application in
further sections.
• Lambda Console: Provides a way for you to graphically design your Lambda-based
application, author or update your Lambda function code, and configure event,
downstream resources and IAM permissions that your function requires.
• AWS CLI: A command-line interface you can use to leverage Lambda's API operations,
such as creating functions and mapping event sources.
• SAM Local: A command-line interface you can use to develop, test, and analyze your
serverless applications locally before uploading them to the Lambda runtime.
Design By- Mohit Malviya

13. Introducing AWS Lambda
“A PaaS for event-driven micro-services”
Werner Voegels.
Design By- Mohit Malviya

14. Limitations
• •Monolithic services
• •Hard to evolve(“/ api /1” only)
•
• •Strongly couple done with an other and with clients code
• •Each service encompasses features that may be spreaded across
the whole architecture
• •Services may provide illegitimate features with respect to their
business concerns
Design By- Mohit Malviya

15. Towards a Modular Architecture
Design By- Mohit Malviya

16. Challenges and Enablers
• •Too many resources: O( Nb Of Services x Versions x Environments)
• Finer grained resource mutualisation Is required
• •high work load to setup & manage all these environments
• Better integration of Dev Opstooling
• •Development/ Production environments descrepancies
Design By- Mohit Malviya

17. Aldebaran Technological Context
•Small team of Cloud folks developing «Cloud oriented» applications
•Embedded software developers -Not familiar with Web/Cloud specific constraints
•Scalability?
• •Exploitation?
• •Many languages/ technologies to learn
• –Need tools and methods to easily build and run new services
Design By- Mohit Malviya

18. Design By- Mohit Malviya