How did we move from microservices spaghetti to completely serverless FaaS and GraphQl. Serverless API in Go, with AWS Lambda, API Gateway and DynamoDB.: https://almouallem.net/2019/04/28/serverless-api-in-go-with-aws-lambda-api-gateway-and-dynamodb/

1. FaaS Infrastructure and,
automation.
Channel API

2. Outline
● Whats and Whys
● What are we building

3. Whats and Whys

4. What is FaaS
A paradigm to allow developers to Build, Deploy, and Scale applications at the
FUNCTION level.

5. What is serverless
Serverless is more about the configuration and management of your services in
the cloud, where scaling is managed for you.

6. Serverless is not
only Lambda
functions.
● S3
● ECS fargate
● AppSync
● SQS
● SNS
● API Gateway
FaaS
BaaS

7. Why FaaS
● Simplify the way developers write and run cloud applications
● It helps to apply the principle of least privilege (POLP) which means every
part of the application has minimal access to the data it needs.

8. Blog: https://almouallem.net/2019/04/28/serverless-api-in-go-with-aws-lambda-api-gateway-and-dynamodb/

9. FaaS Infrastructure and,
automation.

10. Elements of FaaS application
● Function code
● Function configuration (Runtime, Memory, environment variables, …)
● Function pipeline

11. Elements of FaaS application
(Code)
● Go
● JavaScript
● Python
● Java

12. Elements of FaaS application
(Configuration)

13. Elements of FaaS application
(CI)

14. What are we building
Channels API

15. History
Previously we had spaghetti architecture where we have N of backend services, talk to what we call
backend to frontend which also talk to each others and channels which talk to multiple backend to
frontend.
Backend services: is a microservices with their own API, documentations and setup.
Backend to frontend: is a microservices with their own API, documentations and setup tailored down to
serve a front application
Channel: is a the user touch point and served by backend to frontend.
.

16. History
Backend to
frontend
Channels
Backend to
frontend
Backend to
frontend
Backend to
frontend
Backend microservices
Channels Channels Channels

17. Channel API a GraphQL layer on top of NEO
Backend microservices

18. Channel API is a FaaS application

19. Channel API built and running in AWS

20. Channel API is completely serverless

21. Channel API is a collaboration between teams in DC domain.

22. Channel API is a FaaS application + AppSync

23. What is GraphQL
GraphQL is a specification by Facebook
implemented in many programming
languages.

24. What is GraphQL
RuntimeQuery language
Schema Resolvers

25. How GraphQL works

26. Describe what your
application can do.

27. Ask for what you need,
and get exactly that.

28. What is AppSync
Managed Graphql Platform by AWS

29. AppSync
RuntimeQuery language

30. We
Schema Resolvers

31. How channel API works

32. Project structure
Two repositories
● Channelapi-aws :
○ Infrastructure code
○ Terraform
● Channel-api-functions:
○ Functions code
○ GraphQL schema
○ Resolver mapping
○ Grafana metrics

33. Infrastructure

34. Infrastructure

35. What do we need to automate
Functions
● Test
● Build
● Zip
● Upload to storage
● Generate Terraform
code
Infrastructure
● Provisioning resources
● AppSync Schema
● AppSync Resolvers
Other stuff
● Grafana dashboard
● Alert
● Logs

36. Functions

37. Infrastructure

38. AppSync resource

39. AppSync resource
● To update AppSync Schema and datasoruces.
● Open source / Telia oss
● Go
● Docker

40. AppSync resource

41. AppSync resource

42. AppSync resource

43. Grafana resource

44. Grafana resource
● To update Grafana dashboard
● Open source / Telia oss
● Rust
● Docker

45. Grafana resource

46. Grafana resource