If the app becomes highly successful and needs to evolve and possibly runs into scalability and maintenance issues, you might regret not having started with microservices...
I'll be honest, this makes me anxious. That is, having built the application to a working state as a monolith (or a few monoliths, in the case of separating the social/learning/dating/e-commerce aspects while still keeping these fairly monolithic) and then needing to figure out a way to convert them to microservices to scale out.
Perhaps by then, it won't be a job for just one developer (me).
I really appreciate your reply. Thanks!
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'll be honest, this makes me anxious. That is, having built the application to a working state as a monolith (or a few monoliths, in the case of separating the social/learning/dating/e-commerce aspects while still keeping these fairly monolithic) and then needing to figure out a way to convert them to microservices to scale out.
Perhaps by then, it won't be a job for just one developer (me).
I really appreciate your reply. Thanks!