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!

News from the World of Software Development – April 2017

Here is another edition of our monthly news digest at the Betica Blog. We search for interesting and relevant stories to provide insights to your daily application engineering activities. Last month’s digest is available at this link, if you are interested in checking it out.

With spring in full force in the Northern Hemisphere, hopefully these stories inspire your own software development efforts.

The “Internet of Trains” improving the Efficiency of Railroads

The German company, Siemens, plans to open a software development center in Atlanta with the goal of making railroading more efficient. Called the Data Analytics and Applications Center, the company’s efforts are dubbed with the “Internet of Trains” moniker. News about Siemens’ Atlanta investment was reported on in the Atlanta Business Chronicle.

Reducing downtime while increasing the mileage for each train requires an increased investment in digital technology with the hopes of modernizing railway infrastructure as well as the trains and boxcars themselves. Siemens is known all over the world for their power transmission and signaling and control technology used in the rail industry. Their Internet of Trains solution also focuses on data analytics and predictive software.

The company’s Director of Mobility Delivery Services Gerhard Kress commented on the goals of the project. “We are heading towards next-generation maintenance. It is all about increasing up-time and avoiding unplanned downtime. If we predict incidents early enough we, and our customers, can react accordingly,” said Kress.

Siemens’ work is another example of how data analytics and Web-enabled devices are ushering in an era of innovation in many different industries.

The VA hoping to outsource Modernization of its COBOL Systems

The venerable COBOL language surprisingly still lurks in many legacy systems in the financial industry and government agencies. The United States Department of Veterans Affairs hopes to finally enter the 21st Century when it comes to its technology infrastructure, and is looking to outsource the reengineering of their application inventory. News about the VA’s planned migration was published earlier in April at FedScoop.

Acting VA CIO Rob Thomas commented on the reasons behind his department’s move away from internal application development. “We’re going full into commercial — we’re going to be doing software-as-a-service, we’re going to be doing platform-as-a-service, infrastructure-as-a-service. We’re getting out of the software development business — it’s not a core competency. I see a future for us where we go digital platform both on the benefits side and the health side,” Thomas explained.

A business opportunity lurks for software development shops and SaaS providers hoping to gain customers from the government sector. A measure of COBOL knowledge would also help these companies when reverse engineering existing systems.

Incorporate Design Thinking for Better Software Architecture

This week, Forbes published another article by Scott Stiner, CEO of UM Technologies discussing how to incorporate design thinking into the software architecture process. We covered Stiner’s approach to Agile software development in last month’s news digest.

Stiner feels design thinking helps quickly create solutions to solve problems while building a superior user experience. “The Design Thinking process also creates a stronger relationship with the client, considering developers will work closely with the client to understand that client’s core customers. The advantages are many in this regard, and they help speed up the overall development process,” said Stiner.

The entire article is filled with useful insights to help your team build better applications that make your customers happy – and satisfied clients lead to more business opportunities.

Keep coming back to the Betica Blog for additional insights and news from the evolving software development world.

Scrum, Lean, Kanban – An Analysis of Agile Frameworks

As Agile continues to mature as a methodology – forged in the fires of real-world software development projects – a variety of Agile frameworks have emerged. Three of these – Lean, Kanban, and Scrum – are arguably the most popular framework examples in the industry. One of these “flavors” may work best for your team, depending on how it builds applications or the specific needs of a particular project.

So lets take a closer look at the top Agile frameworks to help your development organization make a decision on which one fits best. Good luck!

Is it Time to join the Scrum?

Project management pundit, Moira Alexander compared the three popular Agile frameworks for CIO Magazine. We’ll summarize her take on each of them, starting with Scrum, which is beginning to be used in other industries beyond the software development world. Scrum is highlighted by its predefined roles and processes – one example being that the project manager (or facilitator) is referred to as the Scrum Master.

Scrum’s major focus – essentially like Agile itself – is the faster delivery of high quality software. Since project teams are largely expected to be self-organizing, the Scrum Master serves more as a facilitator compared to a traditional project manager. Sprints tend to be more formal, as is the framework itself, which makes it suitable for organizations used to the Waterfall, but wanting to explore a flavor of Agile.

The timeframes of sprints are also more formally defined; lasting anywhere from two to four weeks. Time spent on daily meetings is limited to 15 minutes. Changes to requirements within a sprint are discouraged.

Go Lean for a Waste-free Process

The Lean Agile framework saw its genesis in the manufacturing industry as an attempt to minimize any wasted efforts on a project, while also offering a learning opportunity to the members of the project team. Lean strives for overall systemic improvements while preserving the integrity of the process.

In most cases, Lean demands an even more formalized process than Scrum, making it another Agile framework worthy of consideration for shops coming from more structured and organized methodologies. One exception is the lack of a specific timespan for each sprint. There is also additional flexibility regarding meetings and change requests – they happen when necessary.

Kanban offers the most Flexibility

A framework relying on visual workflows to explain and define the development process, Kanban also provides more flexibility than either Scrum or Lean. Developed in the supply chain world, many software development shops now make it part of how they write code. It focuses on completing the tasks within a project while always striving to improve the underlying processes.

Since Kanban teams are extremely self-organizing, a managerial role isn’t always necessary. There is also a high level of flexibility when it comes to project timelines, the scheduling of meetings, and change control. In short, whatever keeps the project moving forward and the process continuously improving is fair game.

This high level view of the most popular Agile frameworks offers a measure of insight on which one would work best at your shop. Be sure to consider the history and experience level of your development team in addition to your goals for the future.

Stay tuned to the Betica Blog for additional insights and ideas from the evolving world of software development. Thanks for reading!