May 2018 Summaries

Cockroach Labs has been working on developing its brand identity, focusing on creating a brand voice that aligns with its mission to "Make Data Easy." Despite the challenges, the design team has embarked on a journey to refine their brand through visual experimentation, particularly using blog illustrations as a platform to explore and evolve their brand voice. Over the past eight months, they collaborated with over 25 international illustrators to produce more than 40 illustrations, which have enhanced social media engagement and community feedback. The approach involves using literal representations, clever storytelling, and thoughtful metaphors to convey technical concepts and cultural stories, leading to significant insights about audience connection and brand identity. The initiative demonstrates the importance of exploration and adaptability in brand development, paving the way for further refinements in visual design, typography, and color. While the brand journey is ongoing, the team remains agile and optimistic about achieving a cohesive brand identity, acknowledging the contributions of illustrators who have propelled their design efforts forward.

As of May 25, 2018, the General Data Protection Regulation (GDPR) has officially taken effect, prompting a surge of privacy policy updates from businesses striving to achieve compliance. Despite the deadline, many companies, around 60% according to a report by Crowd Search Partners, have yet to meet the new regulations, suggesting there is still time to work towards compliance. Cockroach Labs, recognizing the ongoing challenges businesses face, plans to release additional GDPR-related content, offering insights into database compliance and practical guidance for apps. In the meantime, CockroachDB's geo-partitioning feature is highlighted as a tool to aid compliance efforts by allowing control over the physical layout of table data. The company encourages exploration of this feature through their documentation and a 30-day trial of CockroachDB Self-hosted, illustrated by insights from Kindred's architect Kai Niemi, who manages a large online gaming and gambling platform in the EU and Australia.

CockroachDB 2.0 provides a robust solution for supporting a global customer base while remaining compliant with data privacy regulations by enabling operators to manage infrastructure through a single logical control plane. This new version introduces a cluster visualization feature in its web UI, allowing operators and developers to monitor and manage distributed workloads across a global cluster, enhancing efficiency and resource allocation. Using the fictional startup MovR as an example, the blog illustrates how CockroachDB enables seamless data access for users in different geographic regions, thereby reducing latency issues and avoiding the need for running multiple data centers. The database's PostgreSQL-compatible API allows developers to interact easily while the system manages data placement and replication transparently. The scalable nature of CockroachDB ensures that companies can allocate resources efficiently to handle spikes in demand, making it particularly beneficial for startups with limited operational resources. CockroachDB 2.0 is designed to simplify the deployment of global infrastructure, with further plans to enhance speed and ease of use, offering both a free trial and startup-friendly pricing options to encourage wider adoption.

Kubernetes, known for its scalability and efficiency in managing microservices, presents challenges when it comes to orchestrating databases due to their stateful nature. While orchestration easily handles stateless services by replacing failed instances with new ones, databases require careful coordination because their replicas are not interchangeable and have unique states. To address these challenges, Kubernetes offers StatefulSets and DaemonSets, which allow databases to run within Kubernetes environments by providing persistent identities and dedicated resources. StatefulSets ensure consistent network identities and disk persistence across restarts, benefiting from remote persistent disks, while DaemonSets allocate specific nodes to run databases, minimizing resource contention but limiting dynamic rescheduling. Although running databases in Kubernetes can slightly affect performance, these tools offer viable solutions for integrating databases with Kubernetes' infrastructure. However, the choice between using StatefulSets or DaemonSets involves trade-offs between flexibility and resource management, with performance implications and potential limitations in handling failures.