Amplify as a service only consists of a mobile UI testing/snapshot service and a deployment service. Otherwise Amplify uses existing AWS services.
AWS Lambda and Google Cloud Functions are "Function as a Service" products/offerings, same goes for Azure Functions and Cloudflare Workers.
Lambda is part of Amplify in the sense that Amplify uses Lambda to do some things. For example, you can use Lambda to return some calculation from an API endpoint.
Firebase is a bit more self-contained and comes with more of its "own" serivces, but it integrates well with existing Google Cloud infrastructure. For example, there is a service called Cloud Functions for Firebase that lets you write "server side code" that gets executed when Firebase events happen.
Embedded software engineer (C, Linux) & Engineering manager for 15+ years. Trying application development (in python, go, Dart+Flutter now) as hobby...
Glad you like it!
Amplify as a service only consists of a mobile UI testing/snapshot service and a deployment service. Otherwise Amplify uses existing AWS services.
AWS Lambda and Google Cloud Functions are "Function as a Service" products/offerings, same goes for Azure Functions and Cloudflare Workers.
Lambda is part of Amplify in the sense that Amplify uses Lambda to do some things. For example, you can use Lambda to return some calculation from an API endpoint.
Firebase is a bit more self-contained and comes with more of its "own" serivces, but it integrates well with existing Google Cloud infrastructure. For example, there is a service called Cloud Functions for Firebase that lets you write "server side code" that gets executed when Firebase events happen.
Thank you