Read about our journey, the host of benefits for our customers, our exceptional team, and future roadmap in this Amazon Special Edition.
10 Older Entries »
by Chris Goss
Change management is hard. In everyday production, there are numerous factors working against embracing change. Limited preparation time, whole new show = whole new crew, innumerable planning variables, and the challenge of driving an operational plan based on creative instincts. These are problems that technology is not yet built to solve. Time, training, and education can and will make a dent in our efforts, but creative planning is nuanced, and by nature, human.
So, where do we start? What can production management technology do now to pave the way for future change? Having spent the past two years building Prodicle, our production suite of apps, we hit several pockets of success, while learning from numerous obstacles. Others have ventured down this path as well, and there are several start-ups and moderate size companies that reach out to us about their product offerings. It’s exciting to …[Read more]
Congratulations to Duo Security, which announced that it is to be acquired by Cisco Systems for $2.35b. This is a great outcome for all involved, and I'm very proud of what the team has accomplished.
I worked with Duo for about three years, initially as an advisor and ultimately as Chief Operating Officer running Sales, Marketing, Products, Engineering and Services. I helped grow the company from around $7m in Annual Recurring Revenue (ARR) to about $100m. The company has continued to grow to 700 employees, 12,000 customers and revenues that I estimate could exceed $200m ARR by year end, based on prior published numbers.
Duo is the fastest growing company I've been a …[Read more]
“The Apps Marketplace is more than just a place to list your apps, it comes with a community of like-minded partners, developers and Zendesk experts.”
Meet Gregg. Gregg is the founder of Myndbend Multimedia, Inc. which develops enterprise-level, integrated apps for Zendesk, and provides other SaaS-related services that enhance and expand a platform’s capabilities. For more than 7 years, Myndbend has built apps for clients who need unique functionality within Zendesk to facilitate and automate their processes. Let’s hear more about Myndbend’s journey as a Zendesk development shop.
How did you first get started with Zendesk and what prompted you to build on Zendesk’s platform? Was there a specific problem you were trying to solve?
Myndbend started in 2001 with custom web development projects that demanded heavy customer …[Read more]
But the real magic happens on the backend. This is the ecosystem that really powers your website. One writer has articulated this point very nicely as follows:
The technology and programming that “power” a site—what your end user doesn’t see but what makes the site run—is called the back end. Consisting of the server, the database, and the server-side applications, it’s the behind-the-scenes functionality—the brain of a site. …[Read more]
“Spark and Ignite can complement each other very well. Ignite can provide shared storage for Spark so state can be passed from one Spark application or job to another. Ignite can also be used to provide distributed SQL with indexing that accelerates Spark SQL by up to 1,000x.”–Nikita Ivanov.
I have interviewed Nikita Ivanov,CTO of GridGain.
Main topics of the interview are Apache Ignite, Apache Spark and MySQL, and how well they perform on big data analytics.
Q1. What are the main technical challenges of SaaS development projects?
Nikita Ivanov: SaaS requires that the applications be highly responsive, reliable and web-scale. SaaS development projects face many of the same challenges as …[Read more]
MySQL is one of the most popular database technologies used to build many modern SaaS applications, ranging from simple productivity tools to business-critical applications for the financial and healthcare industries.
Pretty much any large scale SaaS application powered by MySQL uses sharding to scale. In this blog post, we will discuss sharding choices as they apply to these kinds of applications.
In MySQL, unlike in some more modern technologies such as MongoDB, there is no standard sharding implementation that the vast majority of applications …[Read more]
There are manifold ways to collect, visualize, and analyze data… but not all methods are equally useful. VividCortex, however, is singular as a database-centric SaaS monitoring platform, and it's designed to provide you with powerful insights into your system that are both inherently actionable and unique. Within minutes of first booting up VividCortex, users frequently discover new aspects of their system. They understand it in brand new ways, just by viewing our app’s basic dashboards and metrics.
But that's just the start. Even beyond those initial revelations, there are many more powerful insights that VividCortex can provide, if you know how and where to look. These views aren’t entirely automatic, but they’re simple to discover with a few tips. Here are 5 insights easy to see with VividCortex.
Find which queries affect the most rows
Understanding which queries are …[Read more]
Dealing with churn, is one of the most important elements of building a subscription business. While some churn is inevitable over time, too much churn indicates a more fundamental problem: customers aren't finding value in your product.
I wrote an article over at GigaOm on this subject including some examples about how to reduce churn from my experience at MySQL and Zendesk.
Having churn is like rowing a leaky boat. After a while, you spend more time bailing water than moving forward. By contrast, organizations that focus on reducing churn will find that their revenue grows every quarter.
To accurately measure what’s going on, you should begin by breaking out churn (customer cancellation) from …[Read more]
Over the last few years there has been an increasing interest in
immutable data management. This is a big change from the
traditional update-in-place approach many database systems
use today, where new values delete old values, which are then
lost. With immutable data you record everything, generally using
methods that append data from successive transactions rather than
replacing them. In some DBMS types you can access the older
values, while in others the system transparently uses the old
values to solve useful problems like implementing eventual
Baron Schwartz recently pointed out that it can be hard to get decent transaction processing performance based on append-only methods like append-only B-trees. This is not a very strong argument against immutable data per se. …
10 Older Entries »