LAMP Stack Explained in 3 Minutes

Поділитися
Вставка
  • Опубліковано 16 жов 2024
  • LAMP vs. MEAN explained → www.ibm.com/cl...
    Watch "NoSQL vs SQL" lightboard video → • SQL vs. NoSQL: What's ...
    LAMP is a web platform made of four different components - can you guess what the acronym stands for? In this video, Dan Kehn explains what those 4 pieces are and how LAMP differs from other stacks like MEAN and MERN.
    Get started for free on IBM Cloud →
    Subscribe to see more videos like this in the future → ibm.biz/subscri...
    #LAMPStack #Linux #Apache

КОМЕНТАРІ • 16

  • @fene2899
    @fene2899 2 роки тому +13

    Never knew LAMP could build such great shoulders and arms. Guessing MEAN and MERN will help blast lower body. All kidding aside, I also didn't know IBM's been dropping these brief, seemingly quality tech videos on UA-cam for several years. I've only watched a couple so far but really liking what I've seen and will check out more. Thanks!

  • @Flankymanga
    @Flankymanga 2 роки тому +11

    I guess LAMP is better for low to medium utilization monolithic app and MEAN and MERN would be better for large amount of users where site rendering is offloaded to the client and backend is only responsible for providing data.

    • @homebarista
      @homebarista 2 роки тому +2

      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.

    • @coldestbeer
      @coldestbeer Рік тому

      So just use a framework with lamp

  • @joshuaraison
    @joshuaraison 2 роки тому +3

    Expecting more and more videos about web development 😌
    IBM guide for web development would be much appreciated : )

    • @homebarista
      @homebarista 2 роки тому +1

      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: ua-cam.com/video/4kG-Cj7UZKc/v-deo.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). 🤔

  • @punstress
    @punstress 8 місяців тому +1

    As someone looking to get back into web stuff and upgrade my outdated skills, this was so helpful. How do you write backward so well? lol

  • @danielgx83
    @danielgx83 13 днів тому

    nice explanation thanks.

  • @Aalii6
    @Aalii6 2 роки тому +1

    very helpful, thank you!

  • @ayasolaris4971
    @ayasolaris4971 2 роки тому

    How does the server handle multiple requests? Does it create a new terminal for each visitor?
    What happens when 100 people visit the site at the same time?

    • @homebarista
      @homebarista Рік тому

      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
    @pfos 2 роки тому

    could you also include JAMstack in future vids?

    • @homebarista
      @homebarista 2 роки тому

      @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.

  • @EverythingFades
    @EverythingFades Рік тому +3

    Hold the fort, is this dude writing backwards?

  • @murat_t
    @murat_t 2 роки тому

    😂