I think Kubernetes is a very very important topic to be discussing at this point in time. Recommend it for a new years resolution for the site :). Also love to see articles why a heavy framework like Laravel compares to other stacks like MEVN. MEVN with Vuex with Docker has been a godsend to me VS my days with Laravel/Forge in terms of speed. Working with Mongo over MySQL (no migrations) has also been huge time saver. Be interested in seeing a compare and contrast matrix of benefits between stacks/frameworks.
@danaia - I think kubernetes is a great platform/tool. However I dont think it fits well with laracasts. It's an infrastructure decision rather than code based. I would also say it's not in Jeff's wheelhouse (sorry if I'm doing Jeff a disservice) so he, in this instance may not be the best person to do tutorials.
@D9705996 - I think we are going to see more mature orchestration tools (https://containership.io/) where something like Forge may get eclipsed. I assume Jeff is aware of the trends and think some posts around these infrastructure methods could be beneficial to Laravel. Am I wrong to assume if Laravel wants to move to the enterprise, it would need to adopt these deployment services? Never really understood the aspirations of Laravel for the enterprise. The enterprise seems to shy away from PHP from my experience so that may be it. Adoption towards these deployment methods could help change these interpretations.
@DANAIA - Agree completely that the infrastructure that your app lives on is changing, on an almost daily basis. What I disagree is that laracasts is the right place to introduce this. Just like in code, encapsulation is important, it shouldnt matter if you run laravel on kubernetes, lamp, forge, etc. You pick what works for your use case. If I need to scale up from a single server apllication/database server, I'm not going to turn to Jeffrey for help in a laracasts lesson... I'm going to reach out to someone like Chris Fidao who specialises in this area.
There are also numerous tutorials on deploying laravel on kubernetes (and equivalents) so reach for these when needed.
@DANAIA - Agree that Jeff is amazing but you need to understand a good teacher is an expert in their field... Jeff isn't a kubernetes expert (I think) so isn't going to be able to give you the same quality in this area. You need to find a kubernetes expert with z similar style.
E.g. Jamie Oliver is a great chef but he wouldn't be who I'd ask to explain how an oven works!
@D9705996 - In all seriousness, I think it is very important in terms of adoption. Last year I needed to Dockerize Laravel for my project. It ended up very large no matter how much I tried to cull. I was forced to move to a MEVN stack which was so much lighter and easy to deploy. Trust me, I wanted to stay with Laravel but forced out because of its size. I could have used Lumen. But I thought that was risky at the time. We do choose the tools for the trade and nothing fits all the pieces. However, much thought has gone into Laravel and it is building an ecosystem of solutions from markup to delpoyment. So, with that said, there may be some areas of focus that could happen that could increase adoption - hence the request for enterprise level deployment strategies. Like to see Laravel-like patterns move to Express/Node for example and be refactored to be super lightweight. Overall, I think PHP is a hard sell for many nowadays. BTW - I get it that Jeff may not be interested in doing a Kubernetes tutorial. Will not push the request at all. Thanks!
@DANAIA - I agree php has a stigma with traditional developement. I work in a java centric dev house and the laugh at me using php most of the time. However they soon shut up when I show them laravel sourcd code. It's so readable, testable and just works (they want a java version of eloquent)
You advocate using mongo as part of your stack. Why? If you have structured data then there is zero benefit over using a traditional RDMS like mysql. Especially as you need to use jenengers 3rd party addon. That's before considering the technical expertise required to manage a NoSQL environment.
You seem adamant on your view point xo I suspect I can't change that here. Al, I would say is if you feel it's a necessity to have a MEVN setup then we need some one to show us how... I'll look forward to seeing your tutorial series
@D9705996 - Boy I wish I was confident to do a tutorial series. With the lack of tutorials and general documentation it has been a real slog to get a stable and secure system in place on the MEVN side. But once you get Vuex and Mongo/Mongoose, Bulma to play nice within a roll-your-own MVC solution that is only 4mb in size with a light memory footprint - it feels soo nice. So, the main reason I like Mongo is that I can update the model, do all the CRUD without any migrations. Being able to nest arrays within DB is genius. The way I can move around JSON objects and manipulate the arrays within Mongo is simply amazing. Maybe I am missing something and doing it all wrong. But It feels good, works and is performant. .popluate command in Mongoose - perfect. Foreign keys - forget about it - hopefully never again. I urge you spend the time and explore it.
@DANAIA - What you describe sounds superb... but at the same time sounds complex, and probably too complex or niche for here. I would highly recommend if you feel strongly about it as the way forward to write a medium article on you setup. You will then be able to get feedback in the comments to help you improve your skills/article
If you do please share as I would love to read it, especially if you can integrate gitlab ci
