Some companies, due to regulatory requirements, a desire to not get locked into one cloud vendor or the likes, look towards a multi-cloud strategy. With this in mind this post is the first of a few showing some of the same functionality (but with different names) across the top three cloud providers, Microsoft’s Azure, Amazon’s AWS and Google Cloud.<\/p>\n
We’re going to start with the serverless technology known as Lambda Functions (in AWS, and I think they might have been the first), Azure Functions and the Google cloud equivalent Google Cloud Functions. Now, in truth the three may not be 100% compatible in terms of their API but they’re generally close enough to allow us to worry about the request and response only and keep the same code for the specific function. Ofcourse if your function uses DB’s or Queues, then you’re probably starting to get tied more to the vendor than the intention of this post.<\/p>\n
I’ve already covered Azure Functions in the past, but let’s revisit, so we can compare and contrast the offerings. <\/p>\n
I’m not too interested in the code we’re going to deploy, so we’ll stick with JavaScript for each provider and just write a simple echo service, i.e. we send in a value and it responds with the value preceded by “Echo: ” (we can look at more complex stuff in subsequent posts).<\/p>\n
Note: We’re going to use the UI\/Dashboard to create our functions in this post. <\/em><\/p>\n Azure Functions<\/strong><\/p>\n From Azure’s Dashboard<\/p>\n Once Azure has done it’s stuff, we’ll have a resource and associated resources created for our functions. <\/p>\n If all went well you’re now looking at the Echo<\/em> function page.<\/p>\n Let’s now test this function. The easiest way is click the Test\/Run<\/em> option <\/p>\n If all went well you’ll see Echo: Shaggy<\/em> and we’ve basically created our simple Azure Function.<\/p>\n Note: Don’t forget to delete your resources when you’ve finished testing this OR use it to create your own code<\/em><\/p>\n AWS Lamba<\/strong><\/p>\n From the AWS Dashboard<\/p>\n Once AWS has done it’s stuff let’s look at the code file index.mjs and change it to <\/p>\n You’ll need to Deploy<\/em> the function before it updates to use the latest code but you’ll find that, at this time, you’ll probably get errors use the Test<\/em> option. One thing we haven’t yet done is supply trigger. <\/p>\n From the Configuration<\/em> tab you’ll see an API endpoint, in your browser paste the endpoint url and add the query string so it looks a bit like this<\/p>\n Note: Don’t forget to delete your functions when you’ve finished testing it OR use it to create your own code<\/em><\/p>\n Google Cloud Function<\/strong><\/p>\n From the Google Cloud dashboard<\/p>\n <\/br> <\/br> <\/br> and click Run Test<\/em>. If all went well you’ll see the Echo response in the GCF Testing tab.<\/p>\n Finally, when ready click Deploy<\/em> and then we can test our Cloud function via the browser, using the previously copied URL, like this<\/p>\n Note: Don’t forget to delete your function(s) when you’ve finished testing this OR use it to create your own code<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Some companies, due to regulatory requirements, a desire to not get locked into one cloud vendor or the likes, look towards a multi-cloud strategy. With this in mind this post is the first of a few showing some of the same functionality (but with different names) across the top three cloud providers, Microsoft’s Azure, Amazon’s […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[700,705,96,357,706,235],"tags":[],"class_list":["post-10243","post","type-post","status-publish","format-standard","hentry","category-aws","category-aws-lambda","category-azure-2","category-azure-functions","category-google-cloud-functions","category-google-cloud-platform"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/10243","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=10243"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/10243\/revisions"}],"predecessor-version":[{"id":10262,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/10243\/revisions\/10262"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=10243"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=10243"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=10243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
\n
\r\nmodule.exports = async function (context, req) {\r\n const text = (req.query.text || (req.body && req.body.text));\r\n context.log('Echo called with ' + text);\r\n const responseMessage = text\r\n ? "Echo: " + text\r\n : "Pass a POST or GET with the text to echo";\r\n\r\n context.res = {\r\n body: responseMessage\r\n };\r\n}\r\n<\/pre>\n<\/ul>\n\n
\r\n{"text":"Scooby Doo"}\r\n<\/pre>\n<\/li>\n\r\nhttps:\/\/your-function-appname.azurewebsites.net\/api\/Echo?code=your-function-key&text=Shaggy\r\n<\/pre>\n<\/li>\n<\/ul>\n
\n
\r\nexport const handler = async (event, context) => { \r\n console.log(JSON.stringify(event));\r\n const response = {\r\n statusCode: 200,\r\n body: JSON.stringify('Echo: ' + event.queryStringParameters.text),\r\n };\r\n return response;\r\n};\r\n<\/pre>\n\n
\n
\r\nhttps:\/\/end-point.amazonaws.com\/default\/echo?text=Scooby%20Doo\r\n<\/pre>\n
\n
\nFrom the Configuration page<\/p>\n\n
\r\nhttps:\/\/your-project.cloudfunctions.net\/echo\r\n<\/pre>\n<\/li>\n
\nThis defaulted to creating a Node.js runtime. Let’s change our code to the familiar echo code<\/p>\n\n
\r\nconst functions = require('@google-cloud\/functions-framework');\r\n\r\nfunctions.http('helloHttp', (req, res) => {\r\n res.send(`Echo: ${req.query.text || req.body.text}`);\r\n});\r\n<\/pre>\n<\/li>\n
\nOnce everything is deployed then change the test payload to <\/p>\n\r\n{\r\n "text": "Scooby Doo"\r\n}\r\n<\/pre>\n\r\nhttps:\/\/your-project.cloudfunctions.net\/echo?text=Scooby%20Doo\r\n<\/pre>\n