My first 14hrs with AWS Lambda

Serverless! Serverless!! Serverless!!!

Everybody seems to be talking about it.

To some, this movement has come to stay, and today, I decided to give it my all.

Goal: To build RESTful API’s that I can call from postman, both locally and from a remote pc/over the internet

I woke up with the urge to do something new today, that urge pushed me to look into Serverless computing as an add-on to my skillset 😂

Started by just jumping into it. With my first 4 attempts I didn’t achieve my desired results and from that, I learnt 4 ways of not going about it. At this point, my interest had peaked and there was no turning back.

I managed to get my first endpoint out and shared with few friends to check it out and give me feedback.

After some good round of feedback, I decided to go deeper, this time, to create multiple endpoints without going through the stress of creating new functions every time. Did all I could and didn’t achieve desirable results so I did what every dev does, went on google and read and practised with about 5/6/7 😝 articles and I was still not impressed till I came along one that spoke my language (NodeJS + MongoDB).

After a lot of tweaks and frustrations, I made it with a deployed CRUD (Create, Read, Update, Delete) API Endpoints that could be accessed remotely.

My take on AWS Lambda so far

What I like:

What I didn’t like:

I am so excited about this, and I will be publishing another article in a week, on my step by step approach deploying serverless function on AWS. 💃🏽💃🏽💃🏽

Dev Stack Experience:

  • JavaScript => NodeJs
  • NoSQL => MongoDB
  • AWS experience => Cloud Practitioner

Number of tries: 29 || Success: 12

Tools Used:

Professional Scrum Master | Full Stack Developer | Fintech | AWS Obsessed. www.dennismachu.com

Professional Scrum Master | Full Stack Developer | Fintech | AWS Obsessed. www.dennismachu.com