What is Phalcon and what are its top alternatives?
Top Alternatives to Phalcon
Symfony
It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.. ...
Laravel
It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
CodeIgniter
CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps. ...
Lumen
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. ...
Slim
Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself. ...
Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...
ASP.NET
.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...
Phalcon alternatives & related posts
- Open source168
- Php140
- Community122
- Dependency injection122
- Professional114
- Doctrine74
- Organized66
- Modular architecture62
- Smart programming42
- Solid38
- Documentation14
- LTS releases11
- Robust6
- Easy to Learn6
- Bundle5
- Good practices guideline5
- Decoupled framework components5
- Simple4
- Service container4
- Powerful2
- Flexible1
- Too many dependency9
- Lot of config files7
- YMAL3
- Feature creep2
- Bloated1
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.
- Clean architecture500
- Growing community359
- Composer friendly336
- Open source312
- The only framework to consider for php293
- Mvc194
- Quickly develop189
- Dependency injection155
- Application architecture142
- Embraces good community packages129
- Write less, do more57
- Restful routing50
- Orm (eloquent)46
- Artisan scaffolding and migrations43
- Database migrations & seeds42
- Awesome35
- Great documentation33
- Awsome, Powerfull, Fast and Rapid25
- Promotes elegant coding25
- Build Apps faster, easier and better24
- JSON friendly22
- Most easy for me21
- Eloquent ORM20
- Easy to learn, scalability20
- Test-Driven19
- Modern PHP19
- Blade Template18
- Beautiful18
- Security13
- Clean Documentation11
- Convention over Configuration10
- Based on SOLID10
- Cool10
- Easy to attach Middleware9
- Simple9
- Fast8
- Easy to use8
- Laravel + Cassandra = Killer Framework8
- Simpler8
- Get going quickly straight out of the box. BYOKDM8
- Easy Request Validatin8
- Less dependencies7
- Simplistic , easy and faster7
- Its just wow7
- Friendly API6
- Its beautiful to code in5
- Super easy and powerful5
- Great customer support5
- Speed4
- Fast and Clarify framework4
- The only "cons" is wrong! No static method just Facades4
- Easy4
- Active Record4
- Php74
- Laravel Mix3
- Laragon3
- Eloquent3
- Easy views handling and great ORM3
- Minimum system requirements3
- Composer3
- Intuitive usage2
- Laravel Spark2
- Laravel Passport2
- Laravel Nova2
- Laravel casher2
- Laravel Horizon and Telescope2
- Laravel Forge and Envoy2
- Ease of use2
- Cashier with Braintree and Stripe2
- Rapid development1
- Scout0
- PHP38
- Too many dependency26
- Slower than the other two19
- A lot of static method calls for convenience15
- Too many include13
- Heavy10
- Bloated7
- Laravel6
- Confusing5
- Does not work well for file uploads in Shared Hosting4
- Too underrated3
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1
related Laravel posts
Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.
Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.
By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.
Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.
There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.
We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.
As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com



















I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.
Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.
As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.
To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .
CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.
Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.
- Rapid development602
- Open source446
- Great community387
- Easy to learn337
- Mvc249
- Elegant202
- Beautiful code201
- Free180
- Great packages179
- Great libraries167
- Restful55
- Comes with auth and crud admin panel52
- Powerful51
- Great documentation48
- Great for web46
- Python36
- Great orm31
- Great for api27
- All included21
- Web Apps17
- Fast16
- Used by top startups14
- Clean12
- Easy setup11
- Sexy10
- Convention over configuration8
- ORM5
- Allows for very rapid development with great libraries5
- The Django community5
- Mvt3
- Its elegant and practical3
- Great MVC and templating engine3
- Easy to use2
- Easy to develop end to end AI Models2
- Easy Structure , useful inbuilt library2
- Cross-Platform2
- Fast prototyping2
- Full stack2
- Batteries included2
- Easy2
- Great peformance1
- Many libraries1
- Zero code burden to change databases1
- Have not found anything that it can't do1
- Map1
- Scaffold1
- Modular1
- Very quick to get something up and running1
- Just the right level of abstraction1
- Python community1
- Full-Text Search1
- King of backend world1
- Underpowered templating24
- Underpowered ORM19
- Autoreload restarts whole server18
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Admin5
- Configuration hell4
- Not as clean and nice documentation like Laravel3
- Bloated admin panel included2
- Not typed2
- Python2
- Overwhelming folder structure2
- 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.
Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?
- Mvc83
- Easy setup74
- Open source67
- Well documented59
- Community support34
- Easy to learn21
- Easy17
- Fast11
- HMVC10
- Language Suppert7
- "Fast","Easy","MVC"6
- Easy, fast and full functional5
- I think it is best. we can make all types of project4
- Powerful4
- Works on Every PHP Server like shared hostings3
- Open source, Easy to setup3
- Super Lightweight, Super Easy to Learn2
- Customizable2
- Beginner friendly framework2
- CLI1
- 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?
- API32
- Microframework25
- MVC19
- PHP16
- Open source12
- Eloquent11
- Restful & fast framework10
- Illuminate support7
- Composer7
- Brother of laravel and fast4
- Easy to learn4
- Fast4
- Not fast2
- Not fast with MongoDB1
- PHP1
related Lumen posts



























This is my stack in Application & Data
JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
Slack
I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.
But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.
Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?
How do you suggest to make the test to prove wich one is better?
PHP Lumen Yii Slim
- Microframework29
- API25
- Open source21
- Php19
- Fast11
- Restful & fast framework8
- Easy Setup, Great Documentation7
- Good document to upgrade from previous version5
- Clear and straightforward5
- Modular4
related Slim posts
I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.
But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.
Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?
How do you suggest to make the test to prove wich one is better?
PHP Lumen Yii Slim
Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source789
- Great for apis477
- Asynchronous467
- Great community414
- Great for realtime apps385
- Great for command line utilities290
- Node Modules77
- Websockets75
- Uber Simple65
- Great modularity53
- Allows us to reuse code in the frontend53
- Easy to start38
- Great for Data Streaming33
- Realtime29
- Awesome25
- Non blocking IO23
- Can be used as a proxy16
- High performance, open source, scalable15
- Non-blocking and modular14
- Easy and Fun13
- Same lang as AngularJS12
- Easy and powerful11
- Future of BackEnd10
- Fast9
- Cross platform8
- Scalability8
- Mean Stack6
- Fullstack6
- Simple6
- Easy concurrency5
- Great for webapps5
- Easy to use and fast and goes well with JSONdb's4
- Friendly4
- React4
- Fast, simple code and async4
- Typescript4
- Its amazingly fast and scalable3
- Isomorphic coolness3
- Great speed3
- Scalable3
- Control everything3
- Fast development3
- One language, end-to-end2
- Scales, fast, simple, great community, npm, express2
- TypeScript Support2
- Easy to learn2
- Easy to use2
- It's fast2
- Less boilerplate code2
- Blazing fast2
- Not Python2
- Performant and fast prototyping2
- Sooper easy for the Backend connectivity2
- Great community2
- Easy1
- Lovely1
- Event Driven0
- Javascript20
- Bound to a single CPU46
- New framework every day37
- Lots of terrible examples on the internet33
- Asynchronous programming is the worst28
- Callback22
- Javascript16
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Callback functions may not fire on expected sequence6
- Very very Slow6
- Unneeded over complication3
- Breaking updates3
- Unstable3
- No standard approach1
related Node.js 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.











How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
ASP.NET
- Great mvc6
related ASP.NET posts
Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.
This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!
But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?
I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.
Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...
I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.