This post describes how we can send data from YugabyteDB to ClickHouse through YugabyteDB’s Change Data Capture (CDC) feature.
GORM is an Object Relational Mapping (ORM) library for Golang. ORM converts data between incompatible type systems using object-oriented programming languages. An ORM library is a library that implements this technique and provides an object-oriented layer between relational databases and object-oriented programming languages.
In this blog post, we’ll show you how to:
- Start a YugabyteDB cluster on your local Engine.
- Download GORM and configure the sample project.
- Create a simple Go application to run GORM with YugabyteDB.
As global companies engage in app modernization initiatives, their developers find it increasingly difficult to match those efforts with a strong data layer. These developers continue to work with costly monolithic databases like Oracle or DB2 and NoSQL databases that forgo strong data consistency and important relational features. But it’s clear a modern database is required to match the ambition of app modernization.
That’s where the YugabyteDB and VMware Tanzu story comes in.
Before jumping into the feature updates, in case you missed it we announced an update to our naming: Yugabyte Cloud is now called YugabyteDB Managed! So, now with that out of the way, let’s get to the exciting new features in YugabyteDB Managed.
We held our second annual Distributed SQL Summit (DSS) Asia annual conference on the 30th and 31st of March 2022, following great feedback from our initial event and user demand.
This two-day online conference was packed with fascinating presentations, discussions, and demos from customers, partners, and our own experts.
With 35 engaging sessions to choose from, and more than 40 speakers, the conference served as a hub for advocates, partners, customers,
A modern GraphQL API layer for cloud native applications needs to possess two characteristics: horizontal scalability and high availability.
Horizontal scalability adds more machines to your API infrastructure, whereas vertical scalability adds more CPUs, RAM, and other resources to an existing machine that runs the API layer. While vertical scalability works to a certain extent, the horizontally scalable API layer can scale beyond the capacity of a single machine.
When it comes to high availability,
Today, we are announcing new names for our product offerings that were previously referred to as Yugabyte Platform and Yugabyte Cloud. The features and capabilities of these products aren’t changing. However, we hope the new names better capture their underlying features and benefits.
We realized that our previous product names did not properly communicate our vision for the product nor easily identify what our products do. But don’t worry, both YugabyteDB and our company name,
Recently, I came across a sample e-commerce application that demonstrates how to use Next.js, GraphQL engine, PostgreSQL, and a few other frameworks to build a modern web application. The application supports basic e-commerce capabilities such as product inventory and order management, recommendation system, and checkout function. This made me curious as to how much effort it would take to complete a retail application migration from an on-premise to cloud native solution. So I decided to try.
Ebean is a Java-based Object–Relational Mapping (ORM) application. It is more user-friendly and understandable than traditional ORM tools, such as Hibernate. It achieves this by employing a session-less design that eliminates the concepts of detached/attached beans as well as the difficulties related with flushing/clearing.
A distributed SQL database is a single logical relational database deployed on a cluster of servers. The database automatically replicates and distributes data across multiple servers. These databases are strongly consistent and support consistency across availability and geographic zones in the cloud.
At a minimum, a distributed SQL database has the following characteristics:
- A SQL API for accessing and manipulating data and objects
- Automatic distribution of data across nodes in a cluster
- Automatic replication of data in a strongly consistent manner
- Support for distributed query execution so clients do not need to know about the underlying distribution of data
- Support for distributed ACID transactions
But should you run a distributed SQL database in Kubernetes?