Happy to announce that [Next.js][nextjs-url] now has an officially supported example for bootstrapping your projects using [Tigris][tigris-url].

In this blog we focus on how we can dump and restore data stored in Tigris Server, an Open Source Database, using Tigris CLI. This will be demonstrated using our public beta environment.

Overview

At a high level the process looks as follows:

• Setting up Tigris CLI
• Authentication via the CLI
• Performing the data dump or restore

This blog outlines the deployment of Tigris on an Google's Kubernetes Engine (GKE) Autopilot instance.

The installation will use recommended settings for redundancy, allocating more resources than a simple laptop based installation would. For more information on the laptop based installation please consult our previous blog!

If you would rather watch a video, check out the deployment in action on YouTube:

We are excited to announce that Tigris is now available on the Vercel Integrations Marketplace. If you are already using Vercel to develop and ship data-rich applications or considering it for a new application, this integration enables you to add Tigris, an Open Source Ops-free Serverless alternative to MongoDB Atlas, to your Vercel application within a few minutes.

This blog outlines the deployment of Tigris on an AWS managed Elastic Kubernetes Service (EKS). Future blogs we will walk through other aspects of the product setup for Tigris as a service, such as the setup of authentication. Stay tuned!

The installation will use recommended settings for redundancy, allocating more resources than a simple laptop based installation would. For more information on the laptop based installation please consult our previous blog!

If you would rather watch a video, check out the deployment in action on YouTube:

Next.js gives you the best developer experience with all the features you need to build modern, fast production-ready applications. Tigris is the perfect companion for Next.js as it is similarly built with developer experience in mind and is truly serverless: build data-rich features, seamlessly implement search, and easily use it with serverless functions, all without needing to do Ops.

Tigris is an open source developer data platform that makes building data-rich applications a breeze. This is the first of a series of blog posts where we show you how to deploy Tigris in various environments. In the first post of the series we will show you how to set up the Tigris platform on your laptop. In our next posts we will cover deploying Tigris on EKS and GKE.

Google first introduced a real-time search function to its search engine over a decade ago (2010). Today, it is virtually impossible to imagine Google without it. Yet, strangely, real-time and live searches aren't as widespread as they should be. The only real players with comprehensive real-time search capabilities are social media platforms and search engines. App and web developers often avoid adding this functionality because it is either too difficult or they feel it's unnecessary. However, it can be highly useful for e-commerce apps and websites that consistently post fresh content (such as blogs). The last decade saw a shift in the software industry's priorities as greater emphasis has been placed on user experience (UX) and UI design. Knowing how and when to implement real-time search is a crucial skill to have as a modern developer. The following guide will explore what it is and where and when to use it.

Tigris is an open source developer data platform that makes building data-rich serverless applications a breeze. It enables developers to stick to just being developers and not be forced into DevOps.

Tigris uses FoundationDB's transactional key-value interface as its underlying storage engine. In our blog post Skipping the boring parts of building a database using FoundationDB we went into the details of why we chose to build on FoundationDB. To recap, FoundationDB is an ordered, transactional, key-value store with native support for multi-key strictly serializable transactions across its entire keyspace. We leverage FoundationDB to handle the hard problems of durability, replication, sharding, transaction isolation, and load balancing so we can focus on higher-level concerns.

We are starting a series of blog posts that go into the details of how Tigris has been implemented. In the first post of the series, we will share the details of how we have built the multi-model document layer on top of FoundationDB. We will cover the topics of data layout, and schema management.

In our recent blog post Databases are legacy. It's time to rethink data storage and usage, we explored the current landscape and the need to rethink how we deal with data, dropping the legacy definition of a database and instead focusing on the concept of a developer data platform. Let me recap the elements of a developer data platform.