That's a fair point, but I hasten to add that the LAMP stack could certainly be used for a backend REST-based app, too. Its history is long and there's a huge install base, thanks in no small part to popular easy-to-install and extensible frameworks like WordPress. We have another video coming up that will get into MERN by Jamil Spain that will elaborate on the tradeoffs.

So just use a framework with lamp

Thanks Joshua! Would you elaborate, e.g., what are you using for front end dev today and why? Would you like to see more hands-on type videos, best practices, popular alternatives, contrasts (X vs. Y), or something else? Add your suggestions here or reply to the comments in the "what would you like to see" video: kzfaq.info/get/bejne/atF3YKabnLu-e5c.html As an aside, yesterday I was scrubbing through a "Coding interview in React" video and thought it might be an interesting format, i.e., show a paired programming session solving a specific problem. Sort of a Stack Overflow "live Q&A" session. The tricky part is appealing to a wide enough audience and not going too long. I admit thinking a live coding session with a critical job interviewer would be pretty stress-inducing, but it was interesting to see that other programmers work much the same way as I do (e.g., copy/paste sample code, edit, add debug output, run, repeat). 🤔

Sorry for the delayed response! By default, Apache has a unique process per request, but you can configure MPM to have a pool of "worker" processes that are dispatched requests (see httpd.apache.org/docs/2.4/mod/prefork.html for more details). If there is a sudden burst of requests, they're queued up. If requests exceed the number of allocated connections, the requester will get a 500-type error. Part of performance tuning is architecting your web servers such that this event rarely if ever happens. Yet another option is returning a 429 "Too Many Requests" status as the server approaches its limit with a timestamp. Browsers *should* honor that request by retrying with the delay included in the response.

@pfos Interesting suggestion, I hadn't heard about this one! What sort of information are you interested in, e.g., getting started, practice examples, comparisons against other stacks, or something else? If you have a website to share that's implemented with Jamstack, I'd be interested in seeing how it renders the UI and its diagnostics with PageSpeed Insights -- especially, based on what I've read, that Jamstack is serving a mix of CDN-cached pre-rendered content and (client-side) JavaScript for the dynamic parts of a page.

Search on "lightboard videos"