October 2019 Summaries

The DataStax whitepaper "Data Modeling in Apache Cassandra™" provides a guide on choosing the right data model for your Apache Cassandra application in five easy steps. It recommends starting with the application workflow, also known as "query-first design," to determine what types of queries the database will need to support. Developers should iterate between the application workflow and entity relationship diagram (ERD) to identify data items and relationships required by the application. Once a clear understanding of the application workflow and key data objects is achieved, developers can start identifying the necessary queries for the application.

The DataStax whitepaper "Data Modeling in Apache Cassandra" provides a guide on choosing the right data model for your Apache Cassandra application in five steps. Cassandra is popular among architects and developers due to its performance, scalability, continuous availability, geographic distribution, and ease of management. Understanding how Cassandra stores data is crucial for developing an effective data model. Cassandra clusters consist of multiple nodes with redundant storage across nodes according to a replication factor. Tables in Cassandra are similar to RDBMS tables, with physical records spread across the cluster based on partition keys. The partition key is hashed to a 64-bit token that identifies the Cassandra node where data and replicas are stored. Queries using the partition key are fast as they can immediately determine the host holding required data. Since clusters can have many nodes, Cassandra can handle numerous simultaneous queries due to query and data distribution across cluster nodes.

DataStax has announced a new CEO, Chet Kapoor, who will be taking over from outgoing CEO Billy Bosworth. The company started searching for a successor early this year and after intense collaboration between the two leaders, Chet is now leading DataStax into its next phase. Billy expresses his excitement about watching Chet lead the company into the future while also thanking everyone at DataStax for their contributions to the journey so far.

Downtime during peak demand periods like Cyber Monday can result in significant revenue loss for businesses, and it is often due to database complexity rather than hardware or server issues. Modern web applications rely on a variety of databases across hybrid cloud, multi-cloud, and on-premises infrastructure, leading to fragmentation and difficulty in managing operational effectiveness. Using a peer-to-peer masterless database architecture can help mitigate these risks by eliminating single points of failure and allowing for dynamic scaling during high demand periods. Businesses like eBay and Walmart have successfully implemented such architectures to ensure uptime and performance during the holidays.

The author has written a detailed report comparing Apache Pulsar and Apache Kafka, discussing reasons for choosing one over the other. They have added to their previous list of seven reasons with additional points such as multi-tenancy support, quorum replication, tiered storage, end-to-end encryption, stateless components, automatic broker load balancing, and a growing community. The author believes that Pulsar is a legitimate alternative to Kafka, offering similar functionality but with several advantages. They recommend evaluating Apache Pulsar for streaming and queuing systems.

The author has written a detailed report comparing Apache Pulsar and Apache Kafka, discussing reasons for choosing one over the other. They have added to their previous list of seven reasons with additional points such as multi-tenancy support, quorum replication, tiered storage, end-to-end encryption, stateless components, automatic broker load balancing, and a growing community. The author believes that Pulsar is a legitimate alternative to Kafka, offering similar functionality but with several advantages. They recommend evaluating Apache Pulsar for streaming and queuing systems.

Charles Dickens' A Christmas Carol explores themes of transformation and second chances, which are relevant to today's technology landscape. The story follows Ebenezer Scrooge as he is visited by spirits who show him his past, present, and future, ultimately leading to a change in his character. In the world of technology, companies must navigate legacy technical debt while adapting to an increasingly evolving consumer base. This blog takes a look back at how consumer behavior has changed over time, from the mid-to-late 90s with limited internet usage and cautious e-commerce approaches to today's highly mobile and data-driven world. The future holds even more significant changes as emerging technologies converge, such as AI, IoT, AR/VR, and blockchain. These advancements will require businesses to modernize their legacy systems and embrace a data-centric approach in order to thrive in the rapidly evolving marketplace.

DataStax has released a beta version of its Database as a service (DBaaS) offering, Apollo, on both DataStax Constellation and Google Cloud Platform (GCP). Apollo simplifies application development by automating database operations such as provisioning, tuning, configuration, and maintenance. This allows developers to spend more time building applications and less time managing clusters. The beta version is available for testing and feedback, with users able to deploy it directly through DataStax Constellation or the GCP Marketplace.

Research firms predict that by 2020, there will be over 30 billion connected Internet of Things (IoT) endpoints generating massive amounts of sensor data. With the advent of 5G networks and increased mobile use, organizations must rethink their data management strategies to accommodate this influx of new traffic. Developing a cloud strategy that aligns with an organization's unique needs is crucial for success in the IoT world. A hybrid or multi-cloud database model can ensure uptime, high performance, and eliminate data silos, preparing organizations for the upcoming data overload.