A great database manager without platform distinction the best relational option
August 15, 2018
A great database manager without platform distinction the best relational option
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with PostgreSQL
PostgreSQL emerged as a robust option for a re-engineering process that consisted of migrating our business platform from Microsoft SQL server to PostgreSQL. The following were determining factors in our selection: the migration from Borland Delphi to PHP, the ability work in web environments in the frontend of the company, and the product's versatility and ability to adapt to content growth.
- The genetic algorithm that is part of the PostgreSQL core allows the manager to take the most efficient route for the realization of certain queries, which offers superior performance to the options presented as their competitors.
- The possibility of limiting the simultaneous connections that the manager receives allows us to channel their resources efficiently and optimally.
- PostgreSQL allows adding additional languages to Transact-SQL itself to perform its functions or procedures. This is important since it allows teamwork without major limitations to the knowledge of the language being worked, and its availability as an extension for PostgreSQL.
- In short or quick queries, PostgreSQL usually shows disadvantages compared to other, similar applications.
- The knowledge or management of commands by console is desirable. That is to say, it would be better to avoid depending on the graphical interface for the manager to be able to operate it correctly, since the pgAdmin option that this proposes usually consumes a lot of computer resources.
- While it isn't quite bad, the documentation regarding the handler could improve. The current one is usually sufficient, but could improve.
- It allowed the expansion of knowledge towards the free code or open source drivers, difficult subjects to assimilate even for many professionals in the area.
- The process of reengineering allowed us to reorganize a database in order to show an optimal aspect and functioning at this moment.
- Some analysts showed resistance to change by learning something new, despite how enriching this could be for them.
Despite being all open source options, what ended up making us choose PostgreSQL was the robustness of its core, which allows the great workflow that can support timely and efficient response to the demand and demand for resources. In the case of MongoDB, it is a non-relational handler, and the other options showed a lower performance than that offered by PostgreSQL.