Thank you for sharing this! I have similar problem and turned out that serverless is much more time & resource efficient, even though the first time of the migration is a pain the head.
CTO of Cloud Horizon and Vacation Tracker. AWS Serverless Hero, Claudia.js core team member and co-author of 'Serverless Applications with Node.js', published by Manning.
The company I work for is used to the conventional/traditional method. We rent servers somewhere, and do all stuff by ourselves (configuration, maintenance, patching, installing, you name it).
And here it comes, a new project that is asked by the client (which we cannot refuse) to use serverless tech.
As a first-timer, the hardest part of this project is figuring out how the serverless work.
There was one day that one of my API endpoint didn't work. It supposedly return an image, and it just didn't. I spent about almost two days figuring out what on earth happened with my code. Seems like nothing wrong. No error. But it didn't work.
In the end, it turned out there was a config in the serverless part that I missed, and it was solved in a minute by just installing the apigw binary plugin.
CTO of Cloud Horizon and Vacation Tracker. AWS Serverless Hero, Claudia.js core team member and co-author of 'Serverless Applications with Node.js', published by Manning.
Haha, I know that problem :)
There were many weird issues in the last five years, but AWS services are better and better every year. For example, API Gateway HTTP API is a cleaner and more simple version of the REST API.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for sharing this! I have similar problem and turned out that serverless is much more time & resource efficient, even though the first time of the migration is a pain the head.
Thanks! I would love to hear more details. What are you building, and what are your biggest challenges with serverless?
The company I work for is used to the conventional/traditional method. We rent servers somewhere, and do all stuff by ourselves (configuration, maintenance, patching, installing, you name it).
And here it comes, a new project that is asked by the client (which we cannot refuse) to use serverless tech.
As a first-timer, the hardest part of this project is figuring out how the serverless work.
There was one day that one of my API endpoint didn't work. It supposedly return an image, and it just didn't. I spent about almost two days figuring out what on earth happened with my code. Seems like nothing wrong. No error. But it didn't work.
In the end, it turned out there was a config in the serverless part that I missed, and it was solved in a minute by just installing the apigw binary plugin.
I still laugh at it 😂
Haha, I know that problem :)
There were many weird issues in the last five years, but AWS services are better and better every year. For example, API Gateway HTTP API is a cleaner and more simple version of the REST API.