The document proposes a doodle app architecture for Acme Inc. that uses serverless cloud functions to handle image uploads, editing, albums and popularity tracking, stores data in databases, caches photos at the edge with a CDN, and questions Acme Inc.'s requirements, infrastructure needs, and technical expertise to support the app.
4. CLOUD ARCHITECTURE
1. User opens app
2. Request hits endpoint
3. User Login - cognito, auth0, okta,
onelogin
4. Functions - upload, edit, albums,
popular
5. Store user, image, text data
6. Store raw, edited & historical images
7. CDN - cache photos at edge
8. CNAME entry acme.io -> endpoint
5. THOUGHTS ON APP
What type of browsers are supported?
What type of formats need support?
Do we need multi-language support?
How do you measure active users?
6. THOUGHTS ON INFRA
Are your users global or in one region?
What uptime guarantees are required?
Can we lose images (user re-uploads)?
Ex: Instagram & Twitter lose comments sometimes
7. THOUGHTS ON TEAM
Will Acme Inc. support finished app?
Does Acme Inc. have devops expertise?
How about lambda & serverless?
Does Acme Inc know technology X?