Hacker News Reader

Comment by mrweasel | Hacker News Reader

Nice, but the article leaves out the bit about where the API is hosted. It really isn’t the entire web application, just the easy part.

Still a nice guide for static website owner.

View on HN

Hello, author here.

My bad for not giving a more appropriate title for the post. You re right this setup does not take the backend APIs into account. In our case we use Lambda for the backend APIs so that is also serverless but I failed to mention it in the post.

If you do a follow up on how your frontend and the Lambdas work together please post it, that would be super interesting to me.

Hi, also curious how you integrated WhatsApp messages to user for confirmation? Is it business api and is the pricing an issue? (I’m in India too and think WhatsApp api is a bit expensive especially for a use case where I initiated the messaging like in your case)

You could put it in a lambda function.

Not sure why this is downvoted. It’s a perfectly valid “serverless” architecture.

The only downside is that it can get quite messy maintaining.

Where even is the downvote button?

Hidden until you get more karma.

I would guess because then it's "just another serverless web app" and invalidates the title which is "Hosting your ENTIRE web app...".

Hello, Author here.

Could you elaborate on what part of the maintenance would be messy? I was under the impression that maintaining this would be quite easy because there is no physical server present anywhere in this setup.

Not OP, but I think you should be fine. It can get messy if you're using it as a backend for an application that may at some point have different versions in the field (or dev/testing/staging) so you need to support multiple versions of your APIs. It's not impossible, but it can get messy. If anybody has some good rules/frameworks to organize that kind of thing, I'd appreciate a reply.

Reply on news.ycombinator.com