I just used the stack I was used to, didn't really turn out to be the best stack for the job...

Kubernetes is completely unnecessary, although I do enjoy using it.

Having a separate API is kinda nice. I could easily spin up a different front-end like an iOS app and share the same API. And I can write all the server code in Ruby instead of JS, which I prefer to do.

But yeah overall, way over-engineered.

Google does this (but it's still not ideal). Most other crawlers don't. That means they won't see your rendered content.

This becomes an issue with sharing on social media, because your meta tags won't be read properly. If you share a blog post on Twitter for example, it won't be able to fetch your og:image, title etc so it won't look good.

To fix that, you have to use prerendering or server-side rendering. I'm doing hacky stuff with prerendering inside a Cloudflare worker where it detects that it's a crawler and prerenders the page if so.

SPAs also tend to have slow initial load times, which is becoming increasingly important for SEO. You can't avoid at least one additional network call after loading the initial HTML, and if you're not careful you can end up with chained requests for different components etc.

For sites like mine that rely on SEO and social media, it's a pretty big annoyance.