Introduction to event-driven architectures with Apache Kafka on Heroku

Introduction to event-driven architectures with Apache Kafka on Heroku

We live in a world of networked devices, real-time clients, and microservice architectures, which is shifting from transactional to evented interactions. This session will help you understand the shift towards this new generation of evented architectures. It will provide a gentle intro to stateful distributed systems such as Apache Kafka and how they can help you manage high throughput event streams.

This talk was given at Dreamforce on November 7th, 2017, there is a recording: https://www.salesforce.com/video/1773568/

F085bf2092cb300bac787cc5bc65d301?s=128

Ryan Townsend

November 07, 2017
Tweet

Transcript

  1. 2.

    Forward-Looking Statements Statement under the Private Securities Litigation Reform Act

    of 1995 This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
  2. 5.

    “Data is the new oil” “Data is the new oil.”

    Clive Humby, Architect of Tesco’s Clubcard, 2006 “Personal data is the new oil of the internet” Meglena Kuneva, European Consumer Commissioner, 2009 “Data is the new oil” Ann Winblad, Senior Partner at Hummer-Winblad, 2012 “The difference between oil and data is that the product of oil does not generate more oil (unfortunately), whereas the product of data will generate more data”
 Piero Scaruffi, cognitive scientist and author of “History of Silicon Valley”, 2016 “Data is the new oil. The companies that will win are using math.”
 Kevin Plank, founder and CEO of Under Armour, 2016 “Data is the new oil.”
 Richard Titus, CEO AND, 2010 “We’re able to view just everything that they do. [...] Data is the new oil.”
 Bill Diggins, CEO Diggit, 2012 “I want you to think about data as the next natural resource.”
 Virginia Rometty, IBM CEO, 2013 “Information is the oil of the 21st century”
 Peter Sondergaard, SVP Gartner, 2011 “Data is going to be the natural resource for this industrial revolution.” Abhishek Mehta, CEO Tresata, 2013 Source: https://www.quora.com/Who-should-get-credit-for-the-quote-data-is-the-new-oil
  3. 7.

    What we’re going to talk about • What is event-driven

    architecture? • What are the benefits? • What are the downsides? • What is Apache Kafka? • Why use Heroku Kafka? • Use cases & live demos!
  4. 11.

    What is event-driven architecture? I buy something from you ‑

    My bank account goes down, yours goes up
  5. 12.

    What is event-driven architecture? Product views Completed sales Page visits

    Site logins Shipping notifications Inventory received IoT data Weather data Traffic data Tweets Election polling data Tweet!
  6. 13.

    What is event-driven architecture? If this is the way the

    world works, why don’t we model data like this?
  7. 14.

    What is event-driven architecture? Instead we take “snapshots” of state

    at arbitrary intervals and store that as rows in a database.
  8. 18.

    What is event-driven architecture? What if we used an immutable,

    time- ordered sequence of events as our primary store of state?
  9. 22.

    Benefits of event-driven architecture Type Parameters Added Item To Cart

    Item: iPhone X, Quantity: 1 Changed Item Quantity Item: iPhone X, Quantity: 2 Removed Item From Cart Item: iPhone X Added Item To Cart Item: Pixel 2, Quantity: 2 Changed Item Quantity Item: Pixel 2, Quantity: 1 Events
  10. 26.

    Benefits of event-driven architecture Item Quantity iPhone X 2 Pixel

    2 1 Carts Type Parameters Added Item To Cart Item: iPhone X, Quantity: 1 Changed Item Quantity Item: iPhone X, Quantity: 2 Removed Item From Cart Item: iPhone X Added Item To Cart Item: Pixel 2, Quantity: 2 Changed Item Quantity Item: Pixel 2, Quantity: 1 Events Cart Items
  11. 27.

    Benefits of event-driven architecture Item Quantity Pixel 2 1 Carts

    Type Parameters Added Item To Cart Item: iPhone X, Quantity: 1 Changed Item Quantity Item: iPhone X, Quantity: 2 Removed Item From Cart Item: iPhone X Added Item To Cart Item: Pixel 2, Quantity: 2 Changed Item Quantity Item: Pixel 2, Quantity: 1 Events Cart Items
  12. 29.

    Benefits of event-driven architecture ⚫ ⚫ ⚫ ⚫ ⚫ ⚫

    ⚫ ⚫ ⚫ Point-to-point Integrations
  13. 41.

    What is Apache Kafka? “Distributed commit log” open-sourced by LinkedIn

    Fault-tolerant and robust Guaranteed at-least-once delivery Chronological ordering (within partitions) Asynchronous pull-based event consumption Topics for granular event access Kafka 1.0 last week ⏰ ⬇ ↔
  14. 43.

    Why Apache Kafka on Heroku? Instant provisioning High-availability out-of-the-box Multi-tenant

    Kafka plans from $100/mo Really easy to share between your applications Thoughtful developer experience ⚡ ↔
  15. 52.

    Some sort of mind blowing conclusion! (this has been left

    intentionally as the original)
 
 Real conclusion: there are so many uses of EDA, you need to play around with it to see how it’ll fit your specific needs, so just give it a go!