This is an automated email from the ASF dual-hosted git repository.
erickramirezau pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git
The following commit(s) were added to refs/heads/trunk by this push:
new 7855f25 Add Kinetic Data to Case Studies, fix Backblaze
7855f25 is described below
commit 7855f251453642df2f1858523049c911e2da34ce
Author: Diogenese Topper <[email protected]>
AuthorDate: Thu Mar 24 11:31:41 2022 -0700
Add Kinetic Data to Case Studies, fix Backblaze
patch by Diogenese Topper; reviewed by Erick Ramirez for CASSANDRA-17479
---
.../modules/ROOT/images/companies/kinetic_data.svg | 22 ++++++++++
.../source/modules/ROOT/pages/case-studies.adoc | 25 ++++++++++-
.../ROOT/pages/case-studies/Kinetic-Data.adoc | 51 ++++++++++++++++++++++
.../modules/ROOT/pages/case-studies/backblaze.adoc | 2 +-
4 files changed, 98 insertions(+), 2 deletions(-)
diff --git a/site-content/source/modules/ROOT/images/companies/kinetic_data.svg
b/site-content/source/modules/ROOT/images/companies/kinetic_data.svg
new file mode 100644
index 0000000..aa32468
--- /dev/null
+++ b/site-content/source/modules/ROOT/images/companies/kinetic_data.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 25.4.1, SVG Export Plug-In . SVG Version:
6.00 Build 0) -->
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink"; x="0px" y="0px"
+ viewBox="0 0 396.2 66.8" style="enable-background:new 0 0 396.2 66.8;"
xml:space="preserve">
+<style type="text/css">
+ .st0{fill:#F36C24;}
+</style>
+<path class="st0"
d="M26.9,38.5l-5.2,5.5v9.9h-9V14.8h9V33l17.3-18.3h10L32.8,32.2l17.1,21.7H39.4L26.9,38.5z"/>
+<path class="st0" d="M54.1,14.8h9v39.1h-9V14.8z"/>
+<path class="st0"
d="M108.3,14.8v39.1h-7.4L81.4,30.1v23.7h-8.9V14.8h7.5l19.4,23.7V14.8H108.3z"/>
+<path class="st0"
d="M147.8,46.6v7.3h-30.3V14.8h29.5V22h-20.5v8.5h18.1v7h-18.1v9H147.8z"/>
+<path class="st0" d="M163.1,22.1h-12.5v-7.4h34v7.4h-12.5v31.7h-9V22.1z"/>
+<path class="st0" d="M189.5,14.8h9v39.1h-9V14.8z"/>
+<path class="st0"
d="M204.2,34.8c0-11.8,9-20.2,21.2-20.2c6.8,0,12.4,2.5,16.1,6.9l-5.8,5.4c-2.6-3-5.9-4.6-9.8-4.6
+
c-7.3,0-12.5,5.1-12.5,12.5c0,7.4,5.2,12.5,12.5,12.5c3.9,0,7.2-1.6,9.8-4.6l5.8,5.4c-3.7,4.5-9.3,7-16.1,7
+ C213.3,55,204.2,46.6,204.2,34.8z"/>
+<path class="st0"
d="M247.8,15.3h15.5c12.4,0,20.8,8.1,20.8,19.5c0,11.4-8.4,19.5-20.8,19.5h-15.5V15.3z
M263,51.8
+ c11.1,0,18.1-7,18.1-17c0-9.9-7.1-17-18.1-17h-12.4v33.9H263z"/>
+<path class="st0"
d="M315.7,43.3H293l-5,11H285l18-39.1h2.8l18,39.1h-3.1L315.7,43.3z
M314.6,40.9l-10.3-22.5l-10.2,22.5H314.6z"/>
+<path class="st0" d="M333.2,17.8h-14.1v-2.6h31v2.6H336v36.5h-2.8V17.8z"/>
+<path class="st0"
d="M376.1,43.3h-22.7l-5,11h-3.1l18-39.1h2.8l18,39.1h-3.1L376.1,43.3z
M375,40.9l-10.3-22.5l-10.2,22.5H375z"/>
+</svg>
diff --git a/site-content/source/modules/ROOT/pages/case-studies.adoc
b/site-content/source/modules/ROOT/pages/case-studies.adoc
index 0a8cc32..cfae2f1 100644
--- a/site-content/source/modules/ROOT/pages/case-studies.adoc
+++ b/site-content/source/modules/ROOT/pages/case-studies.adoc
@@ -138,7 +138,7 @@ We needed something that would handle really high write
throughput and keep scal
[openblock, card-btn text-center]
--------
[.btn.btn--alt]
-xref:case-studies/backblaze.adoc[Read More,window=_blank]
+xref:case-studies/backblaze.adoc[Read More]
--------
------
----
@@ -871,6 +871,29 @@
https://siliconangle.com/2020/10/09/data-firehose-next-generation-streaming-tech
----
[openblock,card-header]
------
+image:companies/kinetic_data.svg[Kinetic Data]
+------
+[openblock,card-content]
+------
+[discrete]
+=== Kinetic Data
+
+“Once it's set up and running it’s hands-off. Quite frankly, it's easy from an
operations perspective. So our customers, they're using Cassandra, but they
don't really realize it. But they do say, ‘it's always up. It's always fast.’
It's all these benefits that you really want the end-user to know about.”
+
+[openblock, card-btn text-center]
+--------
+[.btn.btn--alt]
+xref:case-studies/Kinetic-Data.adoc[Read More]
+--------
+------
+----
+//end card
+
+//start card
+[openblock,card shadow relative]
+----
+[openblock,card-header]
+------
image:companies/locstat_full.png[]
------
[openblock,card-content]
diff --git
a/site-content/source/modules/ROOT/pages/case-studies/Kinetic-Data.adoc
b/site-content/source/modules/ROOT/pages/case-studies/Kinetic-Data.adoc
new file mode 100644
index 0000000..bbd88c2
--- /dev/null
+++ b/site-content/source/modules/ROOT/pages/case-studies/Kinetic-Data.adoc
@@ -0,0 +1,51 @@
+= Kinetic Data
+:page-layout: case-study
+:page-role: case-study
+:description: The Apache Cassandra Community
+:keywords:
+
+image::companies/kinetic_data.svg[Kinetic Data,align="center"]
+
+== Kinetic Data chooses Apache Cassandra to deliver workflow automation
solution
+
+Enterprise workflow automation
+50 employees
+Global 2000 clients and government customers, including the USDA, US Army and
Navy, Federal Reserve, Fairfax County Public Schools, Emory Healthcare.
+
+**Benefits**
+
+* Distributed fault tolerance
+* Load balancing
+* Data durability through replicas
+* Low friction for operations teams
+
+Kinetic Data is a leading provider of enterprise workflow automation software.
Its Kinetic Platform combines custom workflow builds and pre-built solutions
with a low-code environment that enables tech-savvy ‘smarties’ to automate
workflow processes. The platform also features pro-code functionality that
allows architects to custom code for ease of digital transformation, helping
enterprises extend technology investments and lower costs for their systems at
scale.
+
+When it came to developing the Kinetic Platform, John Sundberg, president of
Kinetic Data wanted a data management system that was robust and minimized
friction when using the product: "Everything we do is focused on helping IT and
business professionals, those closest to the problems, build their own
solutions to those issues," says Sundberg, and when it came to building its
workflow platform, Kinetic decided to build atop of Apache Cassandra.
+
+Ultimately, Apache Cassandra was chosen for its robustness. Features including
automatic failover, load balancing, and replication eliminated many headaches
for Kinetic Data and its customers. Additionally, Kinetic Data wanted to reduce
any friction using its products, and the fact Cassandra is open source was
appealing as users would not have to wrestle with licensing concerns.
+
+=== Testimonial quote
+
+"Once it's set up and running it’s hands off. Quite frankly, it's easy from an
operations perspective. So our customers, they're using Cassandra, but they
don't really realize it. But they do say, ‘it's always up. It's always fast.’
It's all these benefits that you really want the end-user to know about."
+-- John Sundberg, president of Kinetic Data
+
+=== Performant at scale
+
+Previously, Sundberg had experienced a low-code system that used SQL Server
underneath, which highlighted a key challenge: Low-code systems have to be
capable of handling the unknown plans of users and how their plans are likely
to scale. Normally, a system architect builds a tech stack for a specific use
case, understanding the performance requirements and potential bottlenecks. A
low-code system, in contrast, provides a framework for someone else to build
what they like.
+
+=== Optimized queries
+
+No matter what is being built, Kinetic Data has to guarantee excellent
performance. In the past, users would build up a form, and performance would be
as they expected initially but as records increased from 5,000 to 50,000 or
500,000 records, users would see a performance drop. Essentially, this is
because SQL will accept and execute an inefficient query and take as long as
needed to return the result. In contrast, Apache Cassandra would refuse such a
query, which meant users would find [...]
+
+=== Fault-tolerant and scalable
+
+“I did not want the environment to be a fear,” says Sundberg. “I wanted users
to be able to say to themselves, ‘I want to create a form this way’ and be able
to go and create it, and when they submitted a form we needed it to fire in the
way they wanted.” Kinetic Data found that SQL wasn’t enabling them to eliminate
the thought process around the database. “A lot of database talk would pop up
when building forms and workflows,” says Sundberg, where they would need to
consider creating an [...]
+
+This has enabled the Kinetic platform, to benefit one of the largest
healthcare organizations in the Southeast US as a self-service portal to reduce
the workload for the IT team. In 2021, the portal was able to track and handle
120,000 tickets and 40,000 incidents quickly, directing the relevant task to
the right individual or internal team. In another example, the Technology
division for Anne Arundel County Public Schools has been able to manage and
track the workflows for 180,000 Chrom [...]
+
+As Kinetic Data abstracts away the complex infrastructure, customers don’t
realize they are using Apache Cassandra, but “they do know it’s always up; it’s
always fast, and it’s all these benefits you want the end-user to know about,”
says Sundberg.
+
+=== About Kinetic Data
+
+Founded in 1998 and headquartered in St. Paul, Minnesota, Kinetic Data is an
enterprise software company with its workflow platform that connects human and
technology interactions across systems of record at scale. Built on the core
tenets of security, scalability, flexibility, and safety, Enterprise
organizations are empowered to transform their entire organization with highly
efficient, automated workflows that reduces labor cost, cost of service
delivery, and risk.
\ No newline at end of file
diff --git a/site-content/source/modules/ROOT/pages/case-studies/backblaze.adoc
b/site-content/source/modules/ROOT/pages/case-studies/backblaze.adoc
index 6bbb2b7..ab437bd 100644
--- a/site-content/source/modules/ROOT/pages/case-studies/backblaze.adoc
+++ b/site-content/source/modules/ROOT/pages/case-studies/backblaze.adoc
@@ -27,7 +27,7 @@ It was at this point that Backblaze investigated distributed
databases, and Apac
For the launch of Backblaze B2 in 2015, the company adopted Ansible for
software provisioning, configuration management, and application deployment and
paired it with Apache Cassandra for its data needs, applying templates and
Reaper for handling repairs. In selecting Apache Cassandra, there were several
vital benefits that made it the preferred choice for the new cloud solution:
-=== Scalable and elastic performance that delivers</h3>
+=== Scalable and elastic performance that delivers
Backblaze needed to see an increase in write throughput as it added more
hosts. “If you need just read throughput, traditional MySQL replication works
great as you can keep stamping out replicas, but we needed write throughput as
well. Cassandra was able to do that out of the box as opposed to using layering
or our own sharding on top of MySQL,” says Sims. Backblaze has also found the
write throughput and scaling with Cassandra have been very nearly linear. “30
machines does mean having [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
