Introducing Structured Query Server posted Tuesday, March 5, 2024 by The Neighbourhoodie Team

In the vast realm of databases, two types have consistently marked their presence – the traditional SQL databases and the more flexible NoSQL counterparts. SQL databases, with their structured nature, have been serving businesses for decades. On the other hand, NoSQL databases, notably Apache CouchDB, have catered to the needs of modern web applications and their semi-structured data requirements.

While both have their distinct strengths, there's often been a wish amongst users and developers for something that combines the two — a tool that brings together the scalability of NoSQL with the precise querying of SQL. In response to this need, Neighbourhoodie presents the Structured Query Server. Designed with feedback from the developer community, this addition aims to address common challenges faced by CouchDB users and offer enhanced capabilities for data analysts.

This blog is going show the features of our Structured Query Server for Apache CouchDB, its application, and how it harmonise the two different approaches.

CouchDB and Docker posted Tuesday, November 3, 2020 by The Neighbourhoodie CouchDB Team

Docker is an extremely popular way of deploying any kind of application in many different environments. Deploying CouchDB is no exception, the CouchDB project even maintains its own set of Dockerfiles, as well as a helm chart to help orchestrate multiple containers as a cluster on Kubernetes.

default.d and local.d posted Tuesday, October 27, 2020 by The Neighbourhoodie CouchDB Team

When we explored how default.ini and local.ini work in unison to provide a coherent configuration and upgrade behaviour, we skipped over one more part of the configuration puzzle.

Local.ini is Never Overwritten on CouchDB Updates posted Tuesday, October 20, 2020 by The Neighbourhoodie CouchDB Team

CouchDB is configured through configuration files on disk. The format of the files is INI.

When it starts, CouchDB reads a series of .ini files to make up the final configuration it is going to start with. This series of .ini files is called the config file chain.

Everything You Need to Know About CouchDB Database Names posted Tuesday, October 13, 2020 by The Neighbourhoodie CouchDB Team

Naming a database does not sound like an exciting activity. But it can be, if you know all the considerations that go into naming a database in CouchDB. Let’s start with the restrictions.

Sharding — Reducing the Number of Shards posted Tuesday, October 6, 2020 by The Neighbourhoodie CouchDB Team

In contrast to increasing the number of shards for a database, reducing the number of shards is not a built-in operation. In addition, as shard splitting is only available in CouchDB 3.x and later, this advice is good for version 2.x as well.

Sharding — Increasing the Number of Shards posted Tuesday, September 29, 2020 by The Neighbourhoodie CouchDB Team

This advice is only true for CouchDB 3.0.0 or later. Next week, we’ll cover increasing the number of shards in CouchDB 2.x.

Sharding — Choosing the Right q Value posted Tuesday, September 22, 2020 by The Neighbourhoodie CouchDB Team

One of CouchDB’s core features is scalability. There are two axis of scalability in CouchDB:

  1. Scaling the amount of data stored
  2. Scaling the number of requests handled

Use JSON Patch to Resolve Conflicts posted Tuesday, September 15, 2020 by The Neighbourhoodie CouchDB Team

CouchDB is unique in the database world because it makes data conflicts first-class citizens of its data model. Normally, databases and applications built on them do a large amount of work to avoid doing this. In many scenarios, this leads to subtle errors and occasional data loss.

Copy Design Docs to Avoid Waiting For Indexes to be Built posted Tuesday, September 8, 2020 by The Neighbourhoodie CouchDB Team

This advice is relevant for all query mechanisms in CouchDB: Views, Mango Queries, and even Search.

Use Type in Doc _id posted Tuesday, September 1, 2020 by The Neighbourhoodie CouchDB Team

When deciding on which data goes into which CouchDB documents, it is commonly helpful to keep track of the type of document. For example, you could have documents for users and documents for articles.

Neighbourhoodie says Goodbye to Greenkeeper: We’re partnering with Snyk to deliver Next Generation Dev Tool Automation posted Thursday, March 5, 2020 by The Neighbourhoodie Team

Berlin, March 5, 2020. Greenkeeper, the pioneering automated dependency update service, is closing doors on June 3rd, 2020. Neighbourhoodie Software, the makers of Greenkeeper, have partnered with developer security company to build the next generation automated dependency update service. All customers and open source users are provided a one-click migration to the new service under Snyk’s stewardship. Neighbourhoodie’s Greenkeeper developers have spent the past six months building out Snyk’s feature set with regards to automated dependency updates, implementing many of the top feature requests of existing Greenkeeper users.

CouchDB Interviews: Joan Touzet posted Wednesday, August 28, 2019 by liv

This is an interview with Joan Touzet. Joan is Head of CouchDB Support at Neighbourhoodie, is a CouchDB committer, and also sits on the Apache Software Foundation Board of Directors.

CouchDB Interviews: Jan Lehnardt posted Wednesday, August 28, 2019 by liv

This is an interview with Jan Lehnardt. Jan is part of the CouchDB Support team at Neighbourhoodie, as well as VP of Apache CouchDB at the Apache Software Foundation.

Join us at the CouchDB Meetup in Berlin! posted Tuesday, August 13, 2019 by liv

Right before ApacheCon Europe in Berlin, we're excited to announce that we're hosting a special CouchDB meetup!

News for Greenkeeper: pnpm, Yarn Workspaces, License Change Alerts and more posted Tuesday, June 25, 2019 by liv

In the months since we've last published new features for [Greenkeeper][1], we have been working on making our service more robust and secure, as well as adding some functionality that you might be interested in. Read on for the changelog!

An Interview about CouchDB with Jan Lehnardt posted Sunday, June 23, 2019 by liv

In case you missed it, our CEO Jan Lehnardt got interviewed in IBM's Database Deep Dives series. In their post, he shares his insight as one of the leaders for the Apache CouchDB project, as well as database design in general. Check it out here!

A Different Approach to Conference Goodies posted Tuesday, June 18, 2019 by team

It was the height of the conference season in Berlin a few weeks ago, with CSSconf EU and JSConf EU happening back to back. At Neighbourhoodie we’re not only participating with our own booth, but our CEOs Simone & Jan are also part of the organising team of JSConf EU and worked tirelessly for the last nine months to help make the weekend a phenomenal success for all attendees, speakers and sponsors.

Congratulations posted Thursday, May 23, 2019 by jan

The entire Greenkeeper team congratulates the folks at Dependabot for their acquisition by GitHub and their integration into the GitHub Platform.

Today, we are excited to learn that more GitHub users are going to benefit from many of the best practices we helped pioneer for developing software with automated support tools.

An Offline-First Todo List with Svelte, PouchDB and CouchDB posted Friday, May 10, 2019 by alex

Today, we’re combining Svelte, the lean and fast frontend compiler, with PouchDB and CouchDB, and building a lightweight, Offline-First todo list app. It’ll sync your todos between multiple devices for offline use and also keep your data in a central backup database.

Introduction to Semantic Release posted Tuesday, April 30, 2019 by liv

(this post was originally released on the Greenkeeper Blog)

In our last blog post, we talked about SemVer and how it helps communicate changes in your software. Now we’ll have a look at taking it a step further and completely automating our software releases. We do this by using a tool called Semantic Release.

Introduction to SemVer posted Tuesday, April 30, 2019 by irina

(this post was originally released on the Greenkeeper Blog)

Why does software have version numbers? Version numbers come in many shapes and forms, but they all have one thing in common: they signify that one release of a piece of software is different from another release of the same software. So one of the reasons software has version numbers is to show progress, e.g version 2.0.0 comes after version 1.0.0.