The application is just going to perform user authentication, registration, push notifications and standard CRUD operations, however, it might have a CRON in the background sending updates to the app.
If I were building this app, I'd go with a Ruby on Rails app and get this all out of the box, and I'd host it on Heroku. Cache (in memory and at CDN layer) for scaling concerns. Plus maintenance will be simple because so many capable devs and documentation. (I like Rails, but there are similar equivalents in different languages)
Serverless is really cool for a few reasons, but I'm struggling to see it being the right fit from what you described. Your comments about it being a decent idea for 100 engineers but not for 10 seem to agree.
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 the MVP, I agree that using a RoR with Heroku architecture will work well.
Also, AWS has expanded its language support for Lambda to 4 languages - Node.js, Python, Java, C#, and Go.
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.
If I were building this app, I'd go with a Ruby on Rails app and get this all out of the box, and I'd host it on Heroku. Cache (in memory and at CDN layer) for scaling concerns. Plus maintenance will be simple because so many capable devs and documentation. (I like Rails, but there are similar equivalents in different languages)
Serverless is really cool for a few reasons, but I'm struggling to see it being the right fit from what you described. Your comments about it being a decent idea for 100 engineers but not for 10 seem to agree.
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.
Thanks for the suggestions Ben!!
For the MVP, I agree that using a RoR with Heroku architecture will work well.
Also, AWS has expanded its language support for Lambda to 4 languages - Node.js, Python, Java, C#, and Go.