My underanding of how technologies interact is limited. Idk why Ruby on rails is a necessary component. Idk when something should be processed on the browser vs requested from a service. Are there comprehensice resources to get a wholelistically view of how/why an entire full stack product is architected?
ㅁ
This guy is either non tech or troll.
You say you want to know how a fullstack application is built but you say Ruby on rails (or a back end) is unnecessary. Do you know what you're speaking?
The best way is to be a junior on a team that builds a product. But you could look into the book "Designing Data-Intensive Applications" for a rough overview of some systems design patterns.
Go join a frontend team and you will find out
Search through YouTube
What do you do at Google if you don't get basic HTTP knowledge?
LC spotted