Why, in the third decade of the 21st century, after 80 years of writing software, data continues to live in two states, hot data in the compute space and cold data in the persistence state? Of course, data is created and manipulated while in a hot state. Ideally, all data would exist entirely in a hot state when you think about it. However, the reality is that due to the way most computers work, it is necessary to keep only the data that is actively in use in a hot state and push all inactive data out to a cold state persistence layer. This hot and cold data perspective raises the question of why we still have to focus so much attention and effort on dealing with data movement between these two states at the software level. In this talk, we will examine what has led us to this point, why we seem stuck here and look at some possibilities for moving forward. You also see real Java demo examples of an event-driven hot state software approach that inspired this rant and line of thought about seeing data in a hot and cold state way and the profound impact on how we develop software.

1. The End
of the
Data Ice Age
Hugh McKee
Developer Advocate
@mckeeh3

2. Compute & Persistence

3. Software Abstraction

4. Could this be the
End of the Data
Ice Age?

15. Compute & Persistence

16. Software Abstraction

17. Software Abstraction

18. Software Abstraction

19. Software Abstraction

22. Let’s look at some code

24. Event-sourcing example

26. CQRS example

31. Micro Streams

59. Event Flow Example

87. Friction-less Abstractions
Database-less
Broker-less
Kubernetes-less
Ops-less
Services-less
Server-less

88. Abstract Complexity
Increase Simplicity
End of the
Data Ice Age
End of ?…

89. “Any sufficiently advanced technology
is indistinguishable from magic”
Arthur C. Clarke

90. The End
of the
Data Ice Age
Hugh McKee
Developer Advocate
@mckeeh3
Thank you
Q&A
GitHub repo