What is Laravel and what are its top alternatives?
Top Alternatives to Laravel
It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.. ...
CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps. ...
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
It makes building web applications simpler, faster, while requiring less code. A modern PHP 7 framework offering a flexible database access layer and a powerful scaffolding system. ...
Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern. ...
The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family. ...
Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching. ...
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...
Laravel alternatives & related posts
- Open source168
- Dependency injection122
- Modular architecture62
- Smart programming42
- LTS releases11
- Easy to Learn6
- Good practices guideline5
- Decoupled framework components5
- Service container4
- Too many dependency9
- Lot of config files7
- Feature creep2
related Symfony posts
I really love Django because it is really fast to create a web application from scratch and it has a lot a facilities like the ORM or the Admin module ! The Python language is really easy to read and powerful, that's why I prefer Django over Symfony.
I use Django at work to make tools for the technicians but I also use it for me to build my personal website which I host on PythonAnywhere, and with a domain name bought on Namecheap.
We needed our e-commerce platform (built using WooCommerce) to be able to keep products in sync with our #pim (provided by #akeneo) which is built in Symfony . We hooked into the kernel.event_listener to send RabbitMQ messages to a WordPress API endpoint that triggers the updated product to rebuild with fresh data.
- Easy setup75
- Open source68
- Well documented60
- Community support35
- Easy to learn22
- Language Suppert8
- Easy, fast and full functional5
- I think it is best. we can make all types of project4
- Works on Every PHP Server like shared hostings4
- Open source, Easy to setup4
- Beginner friendly framework3
- Super Lightweight, Super Easy to Learn3
- Easily Extensible1
- No ORM5
- No CLI1
related CodeIgniter posts
I have used PHP to do end to end developments , using Laravel CodeIgniter frameworks.
I have learned Python. I also developed an online Result management system in CodeIgniter for my school but now want to migrate to Django as the system is expanding. Is it a good idea?
- Rapid development619
- Open source459
- Great community394
- Easy to learn344
- Beautiful code208
- Great packages186
- Great libraries173
- Comes with auth and crud admin panel59
- Great documentation55
- Great for web52
- Great orm35
- Great for api31
- All included24
- Web Apps20
- Used by top startups16
- Easy setup12
- Convention over configuration10
- Allows for very rapid development with great libraries7
- The Django community7
- Its elegant and practical5
- Great MVC and templating engine5
- Full stack4
- Easy Structure , useful inbuilt library4
- Fast prototyping4
- Easy to develop end to end AI Models4
- Easy to use3
- King of backend world3
- Batteries included3
- Have not found anything that it can't do3
- Zero code burden to change databases2
- Full-Text Search2
- Very quick to get something up and running2
- Many libraries2
- Python community2
- Great peformance2
- Just the right level of abstraction2
- Easy to change database manager1
- Underpowered templating24
- Underpowered ORM19
- Autoreload restarts whole server18
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell6
- Not as clean and nice documentation like Laravel3
- Bloated admin panel included3
- Overwhelming folder structure2
- Not typed2
- InEffective Multithreading1
related Django posts
Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.
Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.
For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.
However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.
All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.
- Open source35
- Really rapid framework25
- Good code organization19
- Security best practices10
- Clean architecture7
- Less code5
- Composer friendly4
- Convention Over Configuration4
- CakePhp Book2
- Cake Bake2
- Built-in Validation2
- Ctp view File extension1
- CakePhp inflector1
- Quickly develop1
- Rest Full Apis1
- Robust Baking Tool1
- Follows Good Programming Practices1
related CakePHP posts
- Rapid development847
- Great gems648
- Great community604
- Convention over configuration479
- Great for web349
- Beautiful code344
- Open source311
- Great libraries270
- Active record260
- Easy to learn88
- Easy Database Migrations86
- Makes you happy78
- Great routing62
- Has everything you need to get the job done53
- Great Data Modeling41
- MVC - Easy to start on38
- Easy setup35
- Great caching26
- Ultra rapid development time25
- It's super easy22
- Great Resources17
- Easy to build mockups that work16
- Less Boilerplate14
- Developer Friendly7
- API Development7
- Great documentation6
- Easy REST API creation5
- Great language4
- Haml and sass4
- Easy to learn, use, improvise and update4
- It works2
- Jet packs come standard2
- Easy and fast2
- Convention over configuration1
- Easy Testing1
- It's intuitive1
- Too much "magic" (hidden behavior)20
- Poor raw performance13
- Asset system is too primitive and outdated11
- Bloat in models6
- Heavy use of mixins6
- Very Very slow3
related Rails posts
But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.
But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.
StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.
Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!
#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit
- Easy to manage359
- Plugins & themes349
- Non-tech colleagues can update website content258
- Really powerful245
- Rapid website development143
- Best documentation76
- Product feature set43
- Custom/internal social network34
- Open source13
- Great for all types of websites7
- Huge install and user base5
- It's simple and easy to use by any novice4
- Most websites make use of it4
- Open Source Community4
- Perfect example of user collaboration4
- I like it like I like a kick in the groin3
- API-based CMS3
- Easy To use2
- <a href="https://secure.wphackedhel">Easy Beginner</a>1
- Hard to keep up-to-date if you customize things11
- Plugins are of mixed quality10
- Not best backend UI8
- Complex Organization1
- Great Security1
related WordPress posts
I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.
I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.
Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map
Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.
Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(
Posting my first article. Please have a look and do give feedback.
Communication InAppChat Dating Matrimonial #messaging
- Open source12
- Restful & fast framework10
- Illuminate support7
- Brother of laravel and fast4
- Easy to learn4
- Not fast3
- Not fast with MongoDB1
related Lumen posts
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
I have a final-study project, and I'm responsible for making decisions for what frameworks to use (both front-end and back-end) and the software architecture to adapt.
The project is a web application for a concrete company. The main goal is to calculate what is called OEE (Overall Equipment Effectiveness), meaning simply the efficiency of the machine. The calculation and display of OEE will be in real-time, meaning that this rate will be updated every two minutes, and it will appear in a graph. Also, we have the state of the machines to display whether the machines are working just fine or there is some problem.
This will be done using IoT, meaning that important data will be sent from the machine to the web application that I will create via the API (someone else will be responsible for this matter). Of course, the application will include employees, factories, as well as machines, ... etc.
The most important thing in the application is real-time performance monitoring of machines and the OEE.
A real example of what we want to do => https://evocon.com/
I choose to use Laravel because : - This type of applications could be implemented by Laravel - Me and my colleague have some knowledge and practice with this framework (choosing other technologies like Node.js means a huge learning curve) - Easy documentation and abandon tutorials
The only reason why I choose Vue.js because It goes well with Laravel (from what I have learned).
The second important question, which software architecture should I adapt ? should I use Microservice Architecture or the normal and well-known Monolithic Architecture? I know the benefits and disadvantages of the first and second methods, but I do not want to make a wrong decision.
If I choose microservice for this project, I will use Lumen (PHP Micro-Framework By Laravel).
Should I use micro-frontend as well? Like VuMS, or it's not necessary for this project?
I don't think that the reasons to choose Laravel are enough, so I want to understand the obstacles that I may face during the development.
In the end, I decided to ask and take expert opinions.
NOTE: this web application will be used by other companies, like in the case of evocon.
If there are tips and things that I must know to accomplish this project, please mention them.
Thank you very much.
- Large community941
- Open source805
- Easy deployment757
- Great frameworks481
- The best glue on the web384
- Continual improvements233
- Good old web181
- Web foundation141
- Community packages132
- Tool support123
- Used by wordpress33
- Excellent documentation31
- Used by Facebook26
- Because of Symfony23
- Dynamic Language19
- Awesome Language and easy to implement14
- Cheap hosting14
- Very powerful web language14
- Fast development13
- Flexibility, syntax, extensibility10
- Because of Laravel10
- Easy to learn10
- Easiest deployment8
- Fastestest Time to Version 1.0 Deployments7
- Readable Code7
- Short development lead times7
- Worst popularity quality ratio7
- Most of the web uses it6
- Faster then ever6
- Open source and large community5
- Simple, flexible yet Scalable5
- Cheap to own4
- Is like one zip of air4
- Easy to learn, a big community, lot of frameworks4
- I have no choice :(4
- Has the best ecommerce(Magento,Prestashop,Opencart,etc)4
- Easy to use and learn4
- Large community, easy setup, easy deployment, framework4
- Open source and great framework4
- Great developer experience3
- Used by STOMT2
- Fault tolerance2
- Great flexibility. From fast prototyping to large apps2
- Interpreted at the run time2
- Walk away2
- Hard not to use2
- Safe the planet2
- So easy to learn, good practices are hard to find19
- Inconsistent API16
- Fragmented community8
- Not secure5
- No routing system2
- Hard to debug1
related PHP posts
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.
Our whole Node.js backend stack consists of the following tools:
- Lerna as a tool for multi package and multi repository management
- npm as package manager
- NestJS as Node.js framework
- TypeScript as programming language
- ExpressJS as web server
- Swagger UI for visualizing and interacting with the API’s resources
- Postman as a tool for API development
- TypeORM as object relational mapping layer
- JSON Web Token for access token management
The main reason we have chosen Node.js over PHP is related to the following artifacts:
- Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.