4 ms·
I don't think servers have a lot to do with this -- when you go to a URL, and a page gets returned, why does it matter where the data came from? For example: S
by rev_bird 11y ago
I don't think servers have a lot to do with this -- when you go to a URL, and a page gets returned, why does it matter where the data came from?
For example: Say you've got an AngularJS app sitting in S3 or something, and your backend is a Node.js app running in Lambda. Google finds a link to "random-new-social-network.com/profile/drinchev" somewhere and tries to index it -- their request is routed to "random-new-social-network.com," where Angular recognizes "/profile/drinchev" as a route to a profile for some user named drinchev, pulls in the "profile" template, and spits out your profile, where Google can read it and call it a day.
If you're talking about search engines getting along with Javascript-reliant sites, that's a different story, but I don't think I see the problem.