Keynote: Rethinking Serverless with FLAME - Chris McCord | ElixirConf EU 2024

Поделиться
HTML-код
  • Опубликовано: 29 апр 2024
  • ✨This talk was recorded at ElixirConf EU 2024. If you're curious about our next event, check elixirconf.eu ✨
    Imagine if you could auto scale by wrapping any existing app code in a function and have that block of code run in a temporary copy of the app. No extra complexity. No FaaS nonsense.
    Enter the FLAME pattern.
    Let's keep in touch! Follow us on:
    💥 Twitter: / elixirconfeu
    💥 Facebook: / codesyncglobal
    💥 LinkedIn: / code-sync
    💥 Mastodon: genserver.social/codesync
  • НаукаНаука

Комментарии • 15

  • @dwylhq874
    @dwylhq874 10 дней назад

    Awesome work as always Chris! 😍
    Doing this in any other language/ecosystem would be 10-100x more code/complexity! 🤯

  • @hank9th
    @hank9th 3 месяца назад +21

    I am blown away by how the Elixir community has been consistently producing banger releases for 10 years.
    Right when you think things have matured, all the hard problems have been solved, and we're about to enter a period of slow, boring growth, Jose bursts in and drops static types & Chris comes up with a way to replace all of "serverless" with 200 lines of Elixir code.
    Like, what?

  • @MightyMoud
    @MightyMoud 2 месяца назад +4

    This is eye opening in a million different ways...

  • @srcrip
    @srcrip 3 месяца назад +10

    This was fantastic

  • @goldnutter412
    @goldnutter412 2 месяца назад +1

    Start simple go far ?
    You got this Elixir bros !

  • @MrManafon
    @MrManafon 2 месяца назад +2

    Great talk! I do feel that Chris forgot, midway, that the biggest issue with comments on Hackernews is that most people don’t even perceive that warm nodes handle tens to tens of thousands of requests, unlike in traditional serverless settings - that is where the concern about cold starts originates from. So not only would it be insanely rare for your user to hit a cold start, it would also almost never-ever happen on an usefacing gateway like liveview or api. You use flame for deferred workloads, not for serverlessly serving content to the public.

  • @akaibukai
    @akaibukai 3 месяца назад +2

    Really mind-blowing!

  • @Dominik-K
    @Dominik-K 3 месяца назад +1

    Thanks for the awesome talk, very good points

  • @NatanaelSirqueira97
    @NatanaelSirqueira97 3 месяца назад +1

    This is super cool! Thanks for the greak talk as always and for all the work you put into your projects.

  • @jaeyson
    @jaeyson 3 месяца назад +2

    Great talk!

  • @JaimeIniesta
    @JaimeIniesta 3 месяца назад +4

    Awesome, that's definitely going to replace my current AWS lambda setup and simplify it.
    Has the code for the demos been published?

  • @absowoot
    @absowoot 2 месяца назад +4

    I wonder if Cloudflare is next on Chris' kill list lol

  • @idiomaxiom
    @idiomaxiom 26 дней назад

    This would be so much cooler if my DAU wasn't a Bool....

  • @juliolinarezescobar
    @juliolinarezescobar Месяц назад

    FLAME vs AWS lambda bills