Understanding Foreign Data Wrappers in Postgres and postgres_fdw
The Postgres Operator easily lets you automate your Postgres in Kubernetes, whether it's one or thousands of instances.
Integrated high availability PostgreSQL solution for enterprises with always on requirements.
Hardened, secure, access controlled PostgreSQL to meet advanced security requirements.
The idea of writing a database query that can then go out to an external source may not occur to someone who is not a DBA early on. That is: instead of figuring out how to grab then load multiple data sets into the same store, or configuring your application backend to connect to a bunch of disparate sources, why not use query JOINs like you usually would across tables within one database?
In case you're not familiar, the dblink module in PostgreSQL, along with the concept of database links or linked servers in other DBMSs, has been around for a while. Foreign data wrappers are newer, having been introduced with PG 9+. Postgres now has a lot of foreign data wrappers available and they work with plenty of different source types: NoSQL databases, platforms like Twitter and Facebook, geospatial data formats, etc. My colleague Craig Kerstiens has shared his thoughts on Postgres being a "batteries included" database, and it's so easy to see why.
