In Cassandra Lunch #102, Stefan Nikolovski will discuss Choreography vs Orchestration / Google Workflows. Accompanying Blog: Coming Soon! Accompanying YouTube: https://youtu.be/aM6G9VT9Iiw Sign Up For Our Newsletter: http://eepurl.com/grdMkn Join Cassandra Lunch Weekly at 12 PM EST Every Wednesday: https://www.meetup.com/Cassandra-DataStax-DC/events/ Cassandra.Link: https://cassandra.link/ Follow Us and Reach Us At: Anant: https://www.anant.us/ Awesome Cassandra: https://github.com/Anant/awesome-cassandra Cassandra.Lunch: https://github.com/Anant/Cassandra.Lunch Email: solutions@anant.us LinkedIn: https://www.linkedin.com/company/anant/ Twitter: https://twitter.com/anantcorp Eventbrite: https://www.eventbrite.com/o/anant-1072927283 Facebook: https://www.facebook.com/AnantCorp/ Join The Anant Team: https://www.careers.anant.us

1. Version 1.0
Choreography vs Orchestration / Google
Workflows
In Cassandra Lunch #102, we will discuss Choreography vs
Orchestration / Google Workflows.
Stefan Nikolovski
Engineer @ Anant

2. Choreography vs Orchestration

3. The Choreography approach

4. The Choreography approach

5. The Choreography approach
Pros
● Each step of the flow can be changed
independently.
● Each step of the flow can be scaled
independently.
● No single point of failure.
● Other systems can build on these
events – e.g. a promo-code service
might be interested in the
order_completed event and send out
discount vouchers to the customer.
● The events are useful artefacts on their
own, and can be fed into a data lake to
generate business intelligence reports.
Cons
● End-to-end monitoring and
reporting are difficult.
● Difficult to implement
timeouts.
● The order flow is not explicitly
modelled and exists only as
an emergent property of what
system does. As such, it’s
only captured in the mental
model of someone who
understands the system end-
to-end.

6. The Orchestration approach

7. The Orchestration approach
Pros
● End-to-end monitoring and reporting
are trivial since Step Functions gives
you built-in visualization and audit
histories.
● Easy to implement timeout – e.g. for a
restaurant to accept an order, or for
the total duration of the order.
● Business logic is in one place, and it’s
easy to maintain and manage.
● The order flow is modelled and source
controlled. You can literally see it in
the Step Functions console.
● The order flow is modelled and source
controlled. Yes, it’s that important that
it should count as two pros!
Cons
● Have to learn yet another
AWS service.
● At $25 per million state
transitions (which counts
Start and End by the way),
Step Functions is a pricey
service.
● If Step Functions is down,
then no orders can be
processed. Although the
same might be said about
Lambda, EventBridge, or any
services that are critical to the
working of this order flow.

8. The Orchestration approach
● Benefits
● Key Features
● Use Cases

9. Strategy: Scalable Fast Data
Architecture: Cassandra, Spark, Kafka
Engineering: Node, Python, JVM,CLR
Operations: Cloud, Container
Rescue: Downtime!! I need help.
www.anant.us | solutions@anant.us | (855) 262-6826
3 Washington Circle, NW | Suite 301 | Washington, DC 20037