I would probably do parts of an app as a serverless/lambda set of functions. For example: photo processing or video transcoding but the app itself, in this case, might be overkill do be done in a totally serverless mode.
If you decide to go the Rails / Heroku route I suggest the following resources which have been very helpful to me:
Yeah. We have a few Lambda functions sprinkled in which we can mock in test and/or dev. We also use some SaaS services with about the same pattern. It definitely pays to have good habits around wrapping services and then working with them like any part of your app.
You are immediately taking on monitoring and possible deployment complexity with these services but if done right I think it's a helpful approach.
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 agree with Ben.
I would probably do parts of an app as a serverless/lambda set of functions. For example: photo processing or video transcoding but the app itself, in this case, might be overkill do be done in a totally serverless mode.
If you decide to go the Rails / Heroku route I suggest the following resources which have been very helpful to me:
Thanks for the links, some of these posts are amazing! They came at the right time as I'm refactoring a huge Rails app with high response times.
Yeah. We have a few Lambda functions sprinkled in which we can mock in test and/or dev. We also use some SaaS services with about the same pattern. It definitely pays to have good habits around wrapping services and then working with them like any part of your app.
You are immediately taking on monitoring and possible deployment complexity with these services but if done right I think it's a helpful approach.