imalexav
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
Because, yes, Django is a very good framework, and I've built/sold apps with it, but in the end, I can't do everything with Django that I can do with Laravel for web development. I mainly use Python with FastAPI for tasks that Python excels at. In Laravel, there may be a bit of a struggle in the beginning to understand how everything works, but over time, the learning curve more than pays off. Plus, there's Laravel Eloquent (I’m referring to the Active Record pattern), Queues (please don’t bring up Celery—every Python web developer knows how painful it can be), and multi-tenancy. And I haven’t even mentioned Django’s async capabilities, haha.
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
May I ask, how much stronger the baseline will be in coparison to another one? Like what are the pros you see in your baseline than the others? This is a very interesting thought of you and I would like to understand it.
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
Look, I get where you're coming from with those 2 cents, but I gotta disagree big time.
Here's the deal with startups:
When you're doing a startup, you need to ship fast. Period. And yeah, you hope whatever tech you pick now will still work when you're big time. But Elixir? Come on. That's not it. Nuxt? Maybe. It's getting better, and I dig how balanced the Nuxt ecosystem is. But it's not always the best for starting out.
You're talking about bills and teams like we're already big. Let's get real.
For a startup, you need:
1. React on the frontend = huge dev pool
2. Something like Python or Laravel on the backend = another huge dev pool
Why? So later, when you actually need to scale, you can easily split it up, make an API, whatever. You've got options and people to hire.
- Nuxt can do the job, sure. But you'll spend more time setting stuff up than building features.
- Laravel? It's faster to get going. Everything you need is right there.
With Laravel, you can crank out any kind of SaaS fast. I'm talking ship a product in a week fast. Try that with Nuxt, and you'll spend most of your time configuring stuff Laravel gives you out of the box.
1. Start with Laravel. Ship something in a week.
2. If your product actually takes off, then think about bringing in Nuxt.
Nuxt is great when you know you're getting bigger and need that extra flexibility and stability. But for starting out? Laravel all the way.
You're choosing the path with the least barriers:
1. Ship fast
2. Find devs easily
3. Keep moving forward
That's what matters for a startup. Not some theoretical perfect tech stack that'll slow you down when you're trying to get off the ground.
And hey, if someone tells you to use Elixir for your MVP, just smile and nod. Then go back to your Laravel project and actually build something while they're still setting up their "perfectly scalable" system. Remember, you can't scale what doesn't exist!
This is just my perspective
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
I consider forntend to be that apart where im building the UI for my user. That what React and Vue was build for. Nuxt does the frontend jobs very well. Backend is where I write mostly my logic of how the things shoudl work based on what the user clicks on the UI. THings like crud to databse, authorisation, analysis of data, convert files, create files, parse files, process some data throught my ml process which can be another external microservice(for example a pytohn fastapi api).
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
And if I want to stat with Nuxt, and then there will be a tiem to add more fucntionality which will force me to add a backend. What are the choices for a TypeScript backend?
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
Thank you for your clarifications! 😊 So, it seems that using PHP (with Laravel) for the backend might be a better choice than using TypeScript. However, this would require me to learn PHP as well. My project, like 95% of web apps, needs features like datasets, authorization, and underlying configuration. If I choose PHP for the backend, it makes sense to start with Laravel. Then, as the project grows, I can add Nuxt to separate the frontend. This would mean working with two languages.
I feel like starting with Laravel and later converting it to an API-only backend while adding Nuxt for the frontend might be quicker overall compared to starting with Nuxt and then building the backend.
This is what I'm trying to understand: What is the better approach? Should I start with Nuxt or Laravel, and why?
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
All these solutions we’ve discussed offer similar benefits in terms of speed, costs, scalability, ecosystem health, and engineer availability. My question is whether I should stick with one main language, TypeScript, or opt for a dual approach using both PHP and TypeScript. I’m reaching out to people with more experience in this area to get their insights.
Specifically, if I choose Nuxt for the MVP and later add a backend, will that actually be faster? It seems like it might not be, due to the potential issues with packages and modules that could become unsupported, forcing you to fix them instead of focusing on shipping. On the other hand, if I choose PHP with Laravel, everything is in one place and tends to be more reliable, since it’s mostly maintained by a core team and is consistently supported.
So, the question boils down to this: Should I start with Nuxt and then add a backend later (which could be anything, even .NET), or should I go with Laravel from the start because it has Blade for templating and is a full-fledged backend framework, and then add Nuxt later?
It can be that I understood you wrong so please correct me if it is so.
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
I'm trying to decide between two approaches for my project. Should I choose PHP with Laravel for the backend and later introduce Nuxt as the frontend? Or should I start with Nuxt and then build a backend? In the first scenario, I would need to work with two languages (PHP and TypeScript), while in the second, I'd primarily focus on TypeScript. However, I'm really drawn to the Laravel ecosystem because it's well-maintained, stable, and thoroughly documented. And this is mainly because I dont understand good enough the Nuxt ecosystem. For example what could I use as a backend if I choose the Nuxt path? Nitro? Then does Nitro have all these add ons that laravel has?
39 replies
Laravel vs Nuxt: Scalability and Backend Separation in Full-Stack Development
Wow, thank s for the insights!
A bit of background:
I am proficient in Python and intend to use it primarily for data analysis, OCR, and machine learning. I plan to utilize FastAPI to create APIs that access this logic. However, I also need to build a frontend, and I’m debating whether to use PHP (Laravel) or TypeScript (Nuxt.js). Python will be a part of the stack regardless. So, the key decision is where to invest—PHP or TypeScript.
What challenges might I face if I choose PHP, and similarly, what obstacles could arise with TypeScript? For example, with Laravel, I feel that I could maintain a monolithic architecture longer than I might be able to with Nuxt.js. I'm trying to understand how long this would be feasible and whether it truly matters in the long run.
39 replies