Would it be so bad to write your Go app using FastCGI? Let a real web server be the server, and build the app in a fast loading binary that can be restarted fr

Would it be so bad to write your Go app using FastCGI? Let a real web server be the server, and build the app in a fast loading binary that can be restarted from time to time. Force session data externalization from the beginning, and have multiple instances that you can restart from time to time. I know you can cluster Java servlet containers, but those apps tend to too often be initially architected as the "one true immortal process", stuffed full of long lived session data.