You’ve open sourced your relational database manager with PostgreSQL – but how can you keep it secure?

You’ve open sourced your relational database manager with PostgreSQL – but how can you keep it secure?

Webcast There was a time when open source was still – no matter how many decades it had driven software projects – regarded as the playground of hippies and utopians. Bold and brave, yet thrown together, inconsistent and unsecured when compared to more established products.


But as incumbent vendors saw sense and bolted open source offerings onto their product load-outs, or even acquired celebrated open source gathering spots outright, open source suddenly became cool. Normal, even.


For relational databases, and the systems that managed them, this was a smile and nod moment. As early pioneers of open source, there are feature-packed, hugely portable and keenly developed options available for anyone wishing to leave behind a big old vendor, enormous annual fees, and cunningly-constructed vendor lock-in.


All of this can belong to anyone – and it’s available right now. There’s just one catch: Some of those gene ..

Support the originator by clicking the read the rest link below.