The document discusses microservices on AWS. It covers key concepts of microservices including (1) componentization via services, (2) organizing around business capabilities, and (3) treating products not projects. It also discusses infrastructure automation, designing for failure, and evolutionary design. The document then summarizes the technological context and limitations of Aldebaran's monolithic architecture and how microservices and a modular architecture could address these. It introduces Amazon EC2 Container Service and AWS Lambda as tools that can help build and run microservices on AWS through containers and serverless event-driven architectures.

1. Micro-Services sur AWS
Cédric DUPUI – Solutions Architect
cdupui@amazon.fr
@aws_actus

2. Micro
Services
Source: Pixabay

3. #1 Componentization
via Services
Source: littlevisuals.co

4. #2 Organized around
Business Capabilities
Source: http://moicani.over-blog.com/2014/03/hey-monsieur-l-homme-orchestre.html

5. #3 Products
not Projects
Source: lyzadanger via Wikimedia Commons

6. #4 Smart endpoints
and dumb pipes
Source: David Shankbone via Wikimedia Commons

7. #5 Decentralization
Source: Ishift via Wikimedia Commons

8. #6 Infrastructure
Automation
Source: Vincent Diamante via Wikimedia Commons

9. #7 Design
for failure
Source: Robert Lawton via Wikimedia Commons

10. #8 Evolutionary
Design
Source: http://themetapicture.com/evolution-of-a-gamer/

11. Aldebaran
Cloud
Services

12. 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
Source: nDevilTV via Wikimedia Commons

13. Limitations
• Monolithic services
• Hard to evolve (“/api/1” only)
• Strongly coupled one with another 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
Source: CATHERINE PRIOR via Wikimedia Commons

14. Towards a Modular Architecture
S3 DynamoDB SQS
EC2DynamoDB

15. µService Model Pros & Cons
• Time to market: Lifecycle releases
of services are “independant”
• Increased evolutivity and new
services creation enabler
• Better control over QoS properties
• Increased workload to set up and
manage multiple environments
• Architecture rationalization
• Services Governance
DevOps Approach
✓ ✗

16. DevOps Methodology & Tooling
Tools of the Trade:
Jenkins, GIT, RedMine, Chef, CloudFormation,
Elastic Beanstalk, Docker (!), etc.

17. Challenges and Enablers
• Too many resources: O( NbOfServices x Versions x Environments )
Finer grained resource mutualisation is required
• high workload to setup & manage all these environments
Better integration of DevOps tooling
• Development / Production environments descrepancies
Container technology can help
DevOps dream is to allow logic to be easily executed
upon events within a specific infrastructure context
that has controlable QoS properties

18. Ideal World …

19. Introducing Amazon EC2 Container Service
http://aws.amazon.com/ecs/
A fully Docker-compatible, fully managed, Linux container service

20. Why Containers ?
Benefits for micro-services
• Speed
• Consistency
• Density / Resource Efficiency
• Flexibility
Source: Pixabay

21. Key Components
• Container-Enabled AMIs
• ECS Agent
• Cluster Manager
• Container Scheduler
• Tasks/Task Definitions
• Repositories / Storage / Networking
Source: Morio via Wikimedia Commons

22. Introducing AWS Lambda
http://aws.amazon.com/lambda/
“A PaaS for event-driven micro-services”
Werner Voegels.

23. AWS Lambda
Respond quickly to new information
Build back-end services that perform at scale
Run your code without managing infrastructure
Cost-effective and efficient

24. NodeJS module
Event Handler
IAM Role for lamda
execution
Resource limits

25. Triggering Events
Lambda function to invoke
Invoking IAM role

26. Inscrivez-vous gratuitement à l’adresse :
aws.amazon.com/summits/paris

27. Thank You