View all

As of jOOQ's 3.13.0 release, jOOQ fully supports CockroachDB. The CockroachDB SQL dialect is now fully supported for future jOOQ and CockroachDB versions.

This past fall, I had the opportunity to intern on the relatively new Bulk I/O team at Cockroach Labs. Our team’s focus is to improve bulk data operations on CockroachDB. My work involved creating a better experience when importing or backing up data without using an external storage service like Amazon’s S3 or Azure’s Blob Service. CockroachDB supports interacting with files in a node’s local storage system, through a feature called nodelocal. However, this has caused confusion and misuse due to its implementation, and the project I took on involved refining the user experience around nodelocal.

Django is a high-level flexible framework for building Python applications quickly. Applications run on Django store data, by default, into a SQLite database file, but lots of Django users find themselves needing to switch to a more performant database in production, one with better availability or scalability.

Welcome, New Roacher! That’s how all of our Welcome Documents start, though you can expect yours to start with your name on top. Welcome Docs are how we help our new teammates get started and get past the natural new job jitters at Cockroach Labs. We understand there’s nothing worse than not knowing what to do or where to go on your first day, so we use Welcome Docs as a nice roadmap for this transition. In a previous blog about onboarding, I share how we structure Your First Weeks at Cockroach. We designed our onboarding process to be robust and informative, covering information about best practices at Cockroach Labs and providing an overview of our product, CockroachDB. However, it doesn’t account for the various nuances of each role, team, or department. That’s why our People team makes an effort to create personalized Welcome Docs to account for those specific role differences. In a partnership with hiring managers, we build the docs to make sure there’s clarity in what’s expected of you in your first 90 days. Here’s a bit more on what they look like:

Hi, I’m Darrien, and I’m building a distributed, near-real time, “OSINT data reconnaissance” system. For this system, I’ll be using CockroachDB for its distributed nature, and connecting it to a .NET Core API via NPoco and Npgsql. In this post, I'll give a walkthrough of how I'm building the system, and how these connections work, so you can use them too.

``` Django includes a full-featured ORM that simplifies interactions with a database--it’s one of the reasons it’s become one of the most popular web frameworks. Even so, you’re still left to manage scale yourself, and ensure the database is resilient and always on. That can be really hard to do with common Django databases like Postgres, SQLite, and MySQL. And that’s why today, we’re excited to announce a new CockroachDB backend for the Django ORM. ``` Using CockroachDB and Django gives you the ease of writing in Python while getting all the benefits of an open source, distributed SQL database. CockroachDB shards automatically, is naturally resilient, and is highly available. Here’s how to get started:

Cloud services abstract away a lot of complexities involved in data center provisioning. Usually, we think of this as a good thing. It’s a huge boon to developer productivity, lowers overhead costs, and allows individual developers and small companies to experiment and grow like never before. But as Rob Reid spoke about at ESCAPE/19, this abstraction obfuscates some darker elements of data center provisioning. Like it or not, cloud computing has real ethical costs attached to it, and due to the “service” part of “cloud services”, we won’t see those costs unless we actively look for them. Reid is a principal engineer at LUSH Digital, and his team has been actively looking at those costs for quite some time now. While he doesn’t purport to have all the answers, his talk on what he’s calling “The Ethical Cloud” invites companies to start asking some of the thornier questions, he spoke openly about these abstractions at ESCAPE/19.

Working at a startup presents a number of challenges for hiring. You have limited resources, you’re lesser-known to those outside of your industry, and you innovate at breakneck speed, making it difficult to articulate what you do. In an industry where candidates are inundated with information, cutting through the noise requires new, ever-evolving strategy.

This article was originally posted on the Kelda.io blog by CEO and Founder, Ethan J. Jackson. Kelda is Docker compose for Kubernetes. It allows you to quickly test your code changes in a remote environment that matches production, without the complexity of interacting with Kubernetes directly. I recently had the pleasure of speaking about Kelda at ESCAPE/19 - the multi-cloud conference, in New York City. It was a fantastic event packed full of sharp folks with interesting perspectives. The talk, How Microservices Enable Multi-Cloud at the Expense of Developers, describes how microservices and CI/CD led to the development of Kubernetes which itself promises to make multi-cloud viable for the first time. However, these advantages are not without costs, particularly for developer productivity. The talk is summarized below.