Event Sourcing and CQRS are design patterns that are great for some domains. The Incident library will help implement them without compromising other parts of your application.
This is the second part of a series of posts that I will present on how your application can use Event Sourcing and CQRS for specific domains with an open-source library that I am developing called Incident. If you haven't read the
Event Sourcing and CQRS are design patterns that are great for some domains. The Incident library will help implement them without compromising other parts of your application.
Event Sourcing and CQRS are design patterns that are great for some domains. The Incident library will help implement them without compromising other parts of your application.
The focus is on enhancing data integrity in your application by adding explicitness between your API and your schema changesets.
Last week I attended Elixir Conf 2019 in Aurora, Colorado. It was my fourth Elixir Conf and by far the one that I engaged more with other people that I've never talked before,
I just came back from Lonestar Elixir Conf 2019 in Austin, Texas. The conference was a single track, 2 days, with an extra day for an optional training (that I didn’t attend
This month CityBase posted an article that I wrote on Elixir umbrella applications, and how this concept can help to build a codebase that can scale. You can read it here: https://medium.