I think you could make serverless work for what you need, but it would depend upon how comfortable everyone was with it. Microservices sound like overkill, you can always create services out of the monolith as you go.
With a serverless architecture you should be able to tie into a queue/event system to handle the cron and other asynchronous events. Depending upon the intended growth of the application you might want to look into using a provider's authentication mechanisms like Amazon's Cognito or the identity provider that is part of Google's Firebase. Those can just get expensive after a certain point.
Recently I have started to use a library/framework called serverless to work with AWS Lambda and Google Cloud Functions. It makes things fairly easy to deploy and lets you get going quickly.
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.
I think you could make serverless work for what you need, but it would depend upon how comfortable everyone was with it. Microservices sound like overkill, you can always create services out of the monolith as you go.
With a serverless architecture you should be able to tie into a queue/event system to handle the cron and other asynchronous events. Depending upon the intended growth of the application you might want to look into using a provider's authentication mechanisms like Amazon's Cognito or the identity provider that is part of Google's Firebase. Those can just get expensive after a certain point.
Recently I have started to use a library/framework called serverless to work with AWS Lambda and Google Cloud Functions. It makes things fairly easy to deploy and lets you get going quickly.