Laravel at Scale: Framework, Community & Ecosystem with Taylor Otwell

Показать описание

This video is part of Adeva Fireside chat Series, where we are hosting chats with industry leaders, covering different tech-specific topics. We are super excited for having Laravel`s creator Taylor Otwell, as our first guest.

In this session with Taylor, we dive fully into Laravel. How it all started, its powerful community and growth, as well as the ecosystem it created for developers. In addition, he answers a lot of questions we received from the attendees before and during the live session.

Don't forget to comment, like, and subscribe :)

0:00 Introduction
1:26 Diving into the beginning of Laravel, what made you decide to build your own framework?
5:10 Tell us a bit about what happened during the period from working as a single person on the framework as a side project, to what is Laravel today?
9:20 What are some of the really useful packages that should be more emphasized, but didn’t get the attention from developers?
11:12 Can you explain a bit more about how things work on Vapor, and how can people use it to build large-scale applications?
14:34 When would you suggest people to use Vapor, instead of Forge for example?
15:33 What are some more interesting projects you know that are currently using Vapor?
18:35 Having in mind that lots of people are not very fond of PHP based on the past when someone comes to you with an argument like that, what`s your best response?
20:18 If we talk about organizing the code or using the things that come with Laravel out of the box, what are some things you would suggest developers who are building apps that are about to scale?
22:04 From your experience, how do you structure your Laravel commercial products, in terms of folders, classes?
23:27 How did you solve scaling issues with your commercial products, if you had any?
26:11 What are some things that are new in Laravel that you would like to share?
29:14 Regarding the Laravel ecosystem, what are some other products or large-scale apps that you would recommend?
30:23 You mentioned Forge, do you plan to continue supporting both Forge and Vapor?
32:07 Are you planning to support MongoDB or NoSQL in general in the future?
33:04 Related to large-scale software, Multitenancy and what’s an approach or solution you can recommend for modern projects in Laravel?
34:30 Do you have any opinion on GraphQL, why it should or shouldn’t be used on projects?
35:15 How would you structure or scale a Laravel site that is heavily reliant on real-time interactions and web sockets?
37:10 Any best practices for local development in Vapor?
38:45 Would Vapor be a good fit for an API-only use?
39:08 Building PCI-Compliance applications, will Vapor become compliant one day, or can we communicate to AWS directly?
40:02 What is the difference between Vapor & Forge when it comes to deploying to AWS? Is it only the serverless that comes with Vapor or are there other differences between the two?
41:10 From your perspective, is there a case when not to use Laravel?
42:33 Do you have some projections about where you want to see Laravel 5 years from now?
43:30 Working full time on Laravel, do you sometimes feel burnt-out at times and are unable to deal with all of this?
45:25 Moving an environment from dev to production, can you speak more about Laravel Sail?
46:35 In general, about Laravel and plans for the future, is there any plan about async base features in Laravel coming up?
47:29 Any opinion around developing more microservice-oriented features using event sourcing, Kafka?
48:17 Are there any next big projects you are working on?
49:36 Talking about CI/CD pipelines, what do you use in the core team with Laravel?
51:22 What are your plans for Lumen, maintaining it, and also including it in Vapor adding native support?
52:45 Do you have any suggestions about keeping up with Laravel upgrades?
54:07 For the next release, do you plan to use any new attributes from PHP 8?
54:50 Final thoughts

#softwareengineering #laravel #php