3. Disclaimer
- This is not a talk about serverless and AWS is great,
but a talk about our experience of going cloud native. -
- Our opinions are our own -
6. Why Navigate?
• No overview of all possible connections
or transit possibilities
• Insufficient transparency in logistic
chains
• Fragmented offer of service providers
in the port
• 25% of all transported containers are
empty
• Insufficient insight in footprint of
connections
• What are my options via Rotterdam?
11. Challenges of Scaling Up
On Premise:
• Typically `always-on` architecture
• High idle times
• Upgrades / updates are slow to role out
• High probability of conflict in multi-tenant systems
• Product isolation is difficult to manage
13. Rethinking Architecture - Requirements?
• Serve: 2 HTTP Get Endpoints
• Ingest: External data suppliers
• Security: Encryption at rest & in-transit
• Scheduling: 2x Daily and ON-Demand
• Performant at scale
14. Client Endpoint API Gateway Lambda DynamoDB
API Gateway, Lambda function & DynamoDB
15. Severless Application Model
“AWS Serverless Application Model (AWS SAM) extends AWS CloudFormation
to provide a simplified way of defining the Amazon API Gateway APIs, AWS
Lambda functions, and Amazon DynamoDB tables…”
https://aws.amazon.com/about-aws/whats-new/2016/11/introducing-the-aws-serverless-application-model/
Serve
26. • Read the docs!
• There is a limit on everything
• Multiple ways to reach you’re goal
• Choose the right service
• YAML Indentations
Lessons Learned