Hands-on Serverless Computing with Go (Udemy.com)

I chose this course because I wanted a quick and fairly detailed introductory course on both Go and AWS. I'm statisfied that I got what I was looking for. This 3hr course took me roughly 5 weekend days to complete; I followed the course properly.The course will need updating soon. Amazon have added new pages and functionality to their dashboards, it can get confusing with all the new additional options that have been added since this course was recorded. For the most part though, it is easy to follow the course - I actually didn't find it to be much of a problem.The biggest issue I had was getting the homemade lambda update utility to be installed in my $path. I figured that out on my own and updated the Q&A section.My next biggest issue is the authors naming of variables, he uses very short and cryptic variable names. For instance `pwv`, I'm guessing means password value; and `lg` for login.On the whole a good course to have in your Udemy library if you need to skill up on GoLang and AWS very quickly and you are not looking for fine details.

Definitely not a beginners course. I can keep up but, I'm having to take a lot of AWS (and some golang) on faith.Nothing in here about how to set up domain initially... that would have been helpful.

Exactly what I wanted to write code in go and upload it as lambda functions

Just watching at a guy coding, with not much explanation.Looking at a sample project has the same value and is much more efficient.

A lot of errors, unclear information

The experience of the course is mainly watching a guy coding. And this feels extremly frustrating for the audience. There is barely any interaction like pausing for a bit and asking questions. Or explanations of why things are done. Either you have a deep understanding of Go. Then there is no point in talking the course. Or you dont - and then you get some source code and have to figure out by yourself what it does. Or why it has been used here.The course would benefit from explanations. Take lecture 2.7 , minute 7:40. Why exactly are we using the $input.path($) syntax here? None given. Only "you just type in this code here". Right, this is not a course about AWS API Gateways. But if youre introducing an AWS service in the course you should present a bit more than the mere basics.To summarize the course: Section 1 covers the introduction of the AWS web interface. Section 2 gives the first basic "Hello World" examples. In section 3 we finally should start with Go and Lambda. Instead were doing some shell scripting with Go for the automatic upload of the source code to S3. Why are we doing this again? No real explanation given. Also the question remains if this is helpful as you would set up a CI pipeline for advanced usage. Why are we suddenly using S3 for the upload? The same feeling here as in section 3: we start to do something - but why? It would have been easier to follow to have a outline of the course at the beginning. There is none. Section 5 is again configuration with setting up SSL.Section 6 - finally a real project. No overview though what were going to build and what technologies we use. Starts as a code along, then at some point the instructor just shows his finished code in lesson 6.22 at minute 9:55. So this is not "were developing an app together and I teach you how you can do it" but rather "I have some already finished sourcecode here which I present to you".One more thing: Vim as an IDE is quite hard to follow with its unique concept of line numbers when you try to code along. Simply not possible when the editor of the instructor changes the line numbers all the time as line 0 is the current line.E.g. Video 6.22, minute 8:31 and the errata pop up: what exactly is line 3 you are referring to? There is no line 3 at that moment even.The course includes the downloadable source code of the examples (why not Github?) so it makes sense to check here as some errors are not fixed in the video. Like in the chat app in users.go it should be hex.DecodeString(s) not hex.Decode(s) as said in the video.Why not simple re-record the video if there are errors in it?Overall the course is far way too short. I would have expected to find a few useful, real-life examples what to do with lambdas. Probably a discussion in what cases lambdas are useful and when not. The course delivers at the end the S3 access and the chat. Which is not that much. It feels incoherent. And lacks any explanation why you should be using Lambda for it. I would have expected to discuss questions like that. There are a ton of interesting questions around Lambda. How does Lamdba work internally? What about the warm up of functions? When to use Lambda and when EC2? None of this is mentioned in the course.I admit that AWS is a complex subject as it is hardly possible to deal with one service without mentioning others. So, no, I did not expect to get a full AWS course. I did in fact take other courses focusing on certain aspects of AWS and they were more helpful. I did expect to get a lot of Lambda and Golang though. And this did not happen.But for me as a student it was a frustrating experience. To be fair and to summarize what you can learn in the course:- How to setup Lambda and using it together with API Gateway.- Writing a local Go script to automatically upload the lambdas via aws-cli- Access S3 Buckets via SDK in Go for working with files- Connect a Domain- Build a chat application with Lambda

Overall very good intro to AWS Lambdas - the one key area for improvement is making clear that you will need an actual domain that you can work with as part of the course - this was not clear upfront (at least to me) and caused some hurdles in the beginning once the course required having admin access to that domain to configure CNAMEs etc... Also the instructor clearly knows his Go inside out but for those less familiar with Go, there were times where he was going too fast to really understand what he was doing without replaying the segment many times.