Training and Workshops

The problem

Most technical training is content delivery with no memory. Someone reads slides, your team nods, and three weeks later nobody can recall the difference between a partition key and a clustering key, let alone design a table that will not fall over at year two.

The training that sticks is built around the decisions your team will actually face on Monday. Not “here is every feature of Cassandra.” Here is the data modeling decision you are about to make. Here are the three ways it breaks in production. Here is how to tell which one you are looking at.

We have been teaching this material for more than a decade through DataStax Academy, conference workshops, the O’Reilly book, and fifty-plus talks. The workshops have been edited down to the parts that change how teams work when they go back to their desks.

What we do

We offer five core workshop formats, each scoped and edited to match what your team is actually working on. We do not run a generic deck at a specific team.

• Cassandra Data Modeling — one-day intro or two-day deep dive for application and backend engineers
• Kubernetes for Data Engineers — one day for platform and data engineers
• Cloud-Native Data Strategy for Leadership — half-day session for CTOs, VPs Data, and architects
• Migration Planning Workshop — one day for engineering leads running a migration
• Custom — scoped to whoever you put in the room and whatever they need to decide

All workshops are delivered on-site by default. Virtual delivery is available as half-day blocks.

What you get

• Live delivery by a senior practitioner, not a trainer running someone else’s slides
• Workshop materials your team keeps: slides, code samples, reference architectures, and a written data modeling or migration plan they produced during the session
• A 60-minute follow-up call two weeks after the session to answer questions that surface once the material hits real code
• The right to reuse internal materials inside your company indefinitely

How it works

Two weeks before. A 60-minute scoping call with the team lead to understand what your engineers are actually working on. We edit the workshop to match.

Week of. On-site delivery. Morning sessions are lecture and discussion. Afternoon sessions are hands-on. A real data modeling exercise against a real problem your team brings to the room. The exercise is the part people remember.

Two weeks after. One hour follow-up call, team-wide. Questions, corrections, and a quick check on whether the material landed.