The only issue was that I was apprehensive of leaning entirely on Gatsby. I find Gatsby to be a wonderful platform for static site generation and have used it to build a few small portfolio sites and blogs. However, long term, you are stuck with a fully static only framework.
Having built a portfolio website using Gatsby already, I absolutely second this conclusion.
To rehash my thoughts (similar to your post): while Gatsby performs very well for its intended static site use-case, it does make the architectural design assumption that the data source is static.
That assumption goes on to become a limitation as soon as requirements imply that data must be dynamic in nature. Migration to another tool is costly, and so (without the powers of foresight) we might be making better use of our time as developers by picking a tool like Next which supports both static and dynamic data use-cases.
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.
Great writeup, Mike!
Having built a portfolio website using Gatsby already, I absolutely second this conclusion.
To rehash my thoughts (similar to your post): while Gatsby performs very well for its intended static site use-case, it does make the architectural design assumption that the data source is static.
That assumption goes on to become a limitation as soon as requirements imply that data must be dynamic in nature. Migration to another tool is costly, and so (without the powers of foresight) we might be making better use of our time as developers by picking a tool like Next which supports both static and dynamic data use-cases.