About SSR, SSG, iSSG, please correct me if I'm wrong.

[grepug]

1. getStaticProps() with fallback: true works only with target: "server" build, not work with serverless build. Also require next start to bootstrap the server.
2. getStaticProps() and fallback: true, require a server to work. And the generated static files store in the file system of the server. And I'm supposed to set a Nginx proxy to handle the requests to those static files.
3. user navigate between pages with <Link /> component also trigger getStaticProps() or getServerSideProps(), and the slow server response can potentially slow down the transition.
4. In my case. I want to deploy my project to a serverless service (I really love Now, but I can't due to some reasons). And my project contains about 4,000 static pages whose data source is changed once a week.
   1. Firstly, I gave up on exporting the 4,000 pages in the build time which is a lot work.
   2. Since getStaticProps() along with getSaticPaths() and fallout came out, I found that it only work with a custom server while I don't want to maintain one.
   3. However getServerSideProps() works great with serverless build, I don't think it is performant that every request to the pages require a backend API call, since they are relatively static.
   4. So, I'd like to have a feature that output a build function in the serverless build which act like the next start with ordinary server build. When a request incoming, it initially calls this build function to check the existence of the generated static file (through a configured location, in my case, it is a url of the cloud storage), generates the files if needs to.

I don't know if there are any misunderstandings above. Please correct me if there is anything wrong!