Best for what purpose? I prefer a database for ACID properties (especially transactions), network availability, scalability, and ease of management (tools): https://en.wikipedia.org/wiki/ACID
Shapefiles permit interoperability with tools that cannot connect to a database, for example, mobile clients without a network connection. Shapefiles may also be a satisfactory and simpler solution for small amounts of data that does not change. In my view, a database is a more powerful and flexible tool to maintain data that changes over time and has defined relationships between its parts. Shapefiles are only a *representation* of data, and can be exported from a database as needed. What are the use-cases? What is the business goal of development? These questions must drive your choice of architecture. Kind regards, Ben. On 24/04/15 09:37, nacer med wrote: > can any one tell me what is the best architecture and why ?? shapefile and > database( postgres) or just database postgres -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
