What is orm? Is proper. Or is eloquent. Do you could implement eloquent?

ORM = Object Relational Mapping

https://en.wikipedia.org/wiki/Object-relational_mapping

It is a set of classes that allow you to access a database with an object oriented approach.

I don't understand what you mean by proper/eloquent but if you are asking whether it is proper to use an ORM vs. the PHP library functions (mysqli_db_connect() etc.) yes it is. As far as eloquence, I personally think it is nicely designed, so yeah it is eloquent.

he probably means Laravel aproach of ORM which name is Eloquent https://four.laravel.com/docs/eloquent

First excuse my English. Exactly Doit76. My question is whether this "ORM" is known or has been designed by the team itself Phalcon. For example codeigniter ORM is "DataMapper" and Laravel and Simfony can work with "Eloquent". My questions can work with some other ORM Thanks!!

Yes Phalcon can work with other ORM, but why you want to use Phalcon if you don't even try to use phalcon ORM which is in 90% similar to Eloquent, and is true C ORM. I used Laravel, it is good framework, but Phalcon is a lot better, I love it :)

Thank you so much. It is true. By your great response. I will work on its own ORM. I was saying about the issue of the scalability of the framework. And if for example you use "Eloquent" to pass easily to Phalcon models.

Jose,

Phalcon has its own ORM that implements the ActiveRecord pattern. In this instance it is the same as the Eloquent implementation.

You can use whatever ORM you like: ZendDb, Eloquent, Propell or anything else. The benefit of using Phalcon is that you get a huge performance increase because of Phalcon's design.

Regarding scalability of the framework, Phalcon can scale nicely depending on the hardware you dedicate to your application and the separation of services i.e. separate web server to db servers etc. Infrastructure changes will help you with scalability more than the framework itself. Having written that Phalcon supports different db connections so that you can easily create db connections for read and others for write.

Have a look at this https://album-o-rama.phalcon.io/ - github: https://github.com/phalcon/album-o-rama/

The application handles 2 million records. So I can safely say it pretty much scales - Note that this app is running on a small EC2 Amazon instance. With Phalcon, you will need to upgrade less frequently your hardware than with another framework purely due to its implementation (as a C extension that is)

Nikolaos, I'm totally convinced. I'm in love with Phalcon. Just a question out of curiosity, was searched but did not find a class or library to create tables, etc. like Schema Builder class. Your can recommend one for use with Phalcom. Thank you very much.

Hi, Edit the previous post, for my bad English. Your I can recommend one for use with Phalcon? Thank

Hi

Out of interest, why did you choose Active Record instead of Data mapper. Phalcon being relatively new, I assumed Data mapper, or some new funky pattern. Active Record looks really dated and messy, took me back to ~2006. Nice project, although ActiveRecord is a big (unexpected) minus.