Barman and repmgr – Essential Tools for PostgreSQL

If your company’s software engineers are veterans with PostgreSQL, chances are pretty good they are also familiar with the utilities, Barman and repmgr. Barman handles the management of the backup and recovery process for a Postgres instance. While repmgr, as hinted at by its name, performs a similar role with replication – in fact repmgr also offers a measure of integration with Barman.

Let’s take a closer look at both tools to see if they make sense as part of your PostgreSQL implementation. If your team is considering Postgres as a cheaper alternative to Oracle, perhaps this additional information helps make your decision easier. Good luck!

Barman – the PostgreSQL Choice for Disaster Recovery

Developed by the well-known purveyor of Postgres support, training, and development, 2ndQuadrant, Barman is a worthy open source option for organizations needing a tool to handle backups and restores for PostgreSQL. It also plays an important role in any company’s disaster recovery process. Barman helps ensure databases are back online as quickly as possible – a vital factor in achieving business continuity.

In fact, Barman focuses its functionality on disaster recovery scenarios. It supports the remote and hot backups of multiple database servers, while helping DBAs or other network personnel get everything up and running again. The tool also provides remote management capabilities for multiple servers, including ssh support.

Other features include the local storage of metadata, PITR (Point-In-Time-Recovery), file compression, retention policies, incremental backups, tar integration, and more. In short, Barman is a fully functional backup and recovery solution for Postgres. Since it is written in Python, companies with developers skilled in that language can make modifications as needed.

Version 2.1 of Barman was released earlier this year. 2ndQuadrant also provides documentation as well as commercial support and consulting options. As an open source software product, a robust online community is available for advice on usage. Any company using PostgreSQL needs to explore Barman as an option for database backup and disaster recovery.

Manage PostgreSQL Replication with repmgr

Another open source Postgres utility developed by 2ndQuadrant, repmgr handles database replication across multiple PostgreSQL servers. The latest version of repmgr – 3.3.1 – was released in March of 2017, supporting Postgres versions 9.3 and later. It leverages streaming replication and the PostgreSQL 9 Hot Standby feature to ensure superior performance in high scalability and availability environments as well as ease of administration.

One of the unsurprising features of repmgr, considering the developer, is its seamless integration with Barman. You are able to make clones from a Barman archive, instead of accessing a live server. This helps prevent a performance hit on a production server.  If live streaming replication gets interrupted, an archive can be easily used in a pinch.

As with Barman, 2ndQuadrant also provides commercial-level support and consulting options with repmgr. When used together, both tools make it easier for companies to build an industry-leading relational database solution at a fraction of the cost of going with Oracle. It is yet another example of the benefits of open source software.

Stay tuned to the Betica Blog for additional news and insights from the wide world of software development. As always, thanks for reading!

News from the World of Software Development – May 2017

Welcome to this month’s collection of a few interesting software development news stories from the last few weeks. If you want to check out April’s news digest, simply click on the following link. Hopefully, the content within this May digest offers a measure of insight for your software engineering activities. Good luck!

Agile making inroads in Government Software Development

Nearing its second decade of use, Agile is finally seeing wide adoption in software development at government agencies. Doug Robinson, the executive director of the National Association of State Chief Information Officers (NASCIO) in the United States reported that 81 percent of state CIOs plan on increasing the usage of Agile and other iterative development methodologies at their shops. News about this Agile implementation growth appeared this week at CRN.

“We’re seeing a lot of excitement in the CIO world to be able to deliver projects on time and within budget using some type of agile methodology,” said Robinson. As government entities tend to be slow to embrace new technology methodologies, this growth in adoption is another obvious sign of the continued maturity of Agile.

Small Teams write more Secure Code

Teams with a small number of developers produce more secure applications compared to groups with more than 20 employees. That is one of the main conclusions from the recently released 2017 CRASH Report, published by CAST Software. As applications grow in size and complexity, they simply become too difficult to manage.

A chief scientist at CAST Software, Bill Curtis, commented on the survey’s findings. “Applications have gotten so big and complex that no single team can understand it all. It might have five or six languages, multiple databases, CRM systems, and you can’t understand all the interactions. That leaves teams making assumptions that in many cases are wrong,” said Curtis.

Shops wanting to write more secure code need to invest in the relevant training for their developers, while giving them the tools for performing both static and dynamic testing. Additionally, involving a third-party team in the final vetting of an application’s security offers a valuable second opinion before the code is deployed to production.

Microsoft switches to Git for Windows Code Source Control

Considering Microsoft’s investment in its own source control systems, it comes as somewhat of a surprise that the tech giant is migrating all the source code for its Windows operating system to the popular open source tool, Git. News about this move appeared this week in Ars Technica.

The reasoning behind this shift lies within Microsoft’s OneCore project which is aimed at simplifying the Windows codebase. Their previous source control solution for Windows, SourceDepot, was straining to handle the massive amount of source code involved, which includes 3.5 million files.

Redmond chose Git because of developer familiarity as well as its open source nature. The basic Git application needed to be updated to seamlessly handle the Windows source code. Microsoft created a fork in the Git code for this purpose and is talking with the other industry giants who use the app – Google and Facebook – about combining their efforts in the future.

Make a visit to the Betica Blog part of your daily routine before firing up your IDE in the morning. As always, thanks for reading!

The NoSQL Capabilities of PostgreSQL

Many businesses of all sizes leverage PostgreSQL as an open source option to Oracle and other relational databases. Significant cost savings while maintaining a similar level of performance remains a preeminent reason for this switch. A robust community and the availability of commercial-grade support make Postgres worthy of consideration for your traditional database needs. 

With NoSQL gaining popularity all over the technology world, you may wonder how PostgreSQL supports this new database paradigm. Let’s take a look at what functionality exists today in the database with a quick towards the future as well.

Postgres NoSQL for the Enterprise

We’ve talked about EnterpriseDB’s commercial level version of PostgreSQL previously on the blog. The company also offers a Postgres version with support for document databases and key-value stores – two of the most common NoSQL database types. Known as Postgres NoSQL for the Enterprise, this is something worthy of closer attention at companies looking for an open source mix of relational and NoSQL databases.

This Postgres database solution combines the speed and flexibility of NoSQL with the traditional SQL database functionality required for enterprise use – most notably the support for ACID (atomic, consistent, isolated, and durable) transactions. Database instances also easily integrate into the existing business data infrastructure, no matter the platform. In short, it provides the best of both worlds – relational and NoSQL.

ACID transactions are vital for business organizations that depend on the real-time validity of the relationships within its data. Many current NoSQL databases don’t offer this feature, instead following the BASE paradigm which emphasizes speed and availability over the consistency of the data. Postgres NoSQL lets companies combine unstructured and structured data; mixing the performance of NoSQL with the more formalized governance of traditional SQL.

Postgres NoSQL supports many industry standards for programmatic access and data exchange. These include Ruby, Python, and JavaScript for the former, and the JSON and XML formats in the latter case. The superior performance of PostgreSQL combined with the seamless scalability typical of a NoSQL database solution make EnterpriseDB’s combination of Postgres and NoSQL a valid option for any business desiring a flexible database infrastructure.

The Future of PostgreSQL and NoSQL

In a previous article looking at new features of PostgreSQL 10, we noted the relative lack of NoSQL functionality in this newest version of Postgres, slated for release later this year. The new XMLTABLE feature supports the direct querying of data stored in XML documents. Other performance improvements in version 10 bring the speed of the relational database closer to its other NoSQL brethren.

One recent enhancement in Amazon Web Services deserves mention for companies using a mixture of relational and NoSQL databases. The AWS database migration service now includes NoSQL databases, with MongoDB (as a source) and Amazon’s own DynamoDB (as a target) being the first two to be supported. This means companies with a PostgreSQL instance on AWS are able to stream data from Postgres to a DynamoDB instance.

Companies with an investment in PostgreSQL need to explore EnterpriseDB’s NoSQL option to see if any of its features make sense for adding non-traditional database formats to the corporate data infrastructure.

Keep returning to the Betica Blog for additional news and insights from the wide world of software development. Thanks for reading!