That is actually the post that got me into event sourcing &#x2F; streams. As far as user analytic type events go this makes complete sense to me. What I haven&#x27;t been able to discern is whether its useful to use this architecture on a much much smaller scale for things that may not be user events.<p>I love the thought of throwing everything into a stream and populating the read models, analytics, search index, etc with the data. However, for example if you had a CMS &#x2F; ecom for a smaller organization, should the admin actions also be events? If you have an event source db, they would have to be, and you get all the benefits outlined from the article.<p>At what point do you decide what to put in the stream and what to build without? Are there events that should never be in a stream? Those are the questions I have been researching but I haven&#x27;t found a lot of resources or discussions around  making these decisions.