Erik Lieben
- @eriklieben
- Software Developer, Effectory
Software Developer at Effectory working from the Netherlands. Organizer of the dotnet.amsterdam meetu...
Read more
Software Developer
- Effectory
- Dec 2006 - Present
2021
May 12, 2021
Spoke at an event
4dotnet pizza session: When events occur
Most developers like to build microservices over monoliths; we want to believe that makes things easier—our teams working autonomously on small systems that are easier to reason about. We tend to overshadow the additional costs, complexity, organizational change, and knowledge required to operate a network of those interconnected (micro)services.
Let alone the scary fact that we now need to reason based upon data that is eventually consistent. In this session, we will look at how to start thinking asynchronously about your system/services.
What can we do to store that flow of events that occur, and what additional value does that bring us. How can we feel safe again about being eventually consistent?
https://twitter.com/Jan_de_V/status/1392539073508777988
Most developers like to build microservices over monoliths; we want to believe that makes things easier—our teams working autonomously on small systems that are easier to reason about. We tend to overshadow the additional costs, complexity, organizational change, and knowledge required to operate a network of those interconnected (micro)services.
Let alone the scary fact that we now need to reason based upon data that is eventually consistent. In this session, we will look at how to start thinking asynchronously about your system/services.
What can we do to store that flow of events that occur, and what additional value does that bring us. How can we feel safe again about being eventually consistent?
https://twitter.com/Jan_de_V/status/1392539073508777988
Apr 21, 2021
Attended an event
Mar 24, 2021
Spoke at a conference
Serverless EventSourcing for pennies using Azure Functions, Storage, and EventGrid
As developers, we store our code in a system (GIT) that allows us to time travel, compare, work together, and reason about our code. We can go back in time to learn who made a particular change, where a bug originated, or which parts of our code have a high change rate. It stores our data/code’s evolution, a proven and valuable practice compared to just keeping the latest state on disk.
Still, as soon as we start building systems ourselves, we (mostly) model our system ‘as if’ we would store code on disk; we only keep the latest state, model it in the way we seem fit at that moment in time, and make it, so it fits in our relational database.
This session will explore the ideas behind event sourcing, a way to store and keep the evolution of data/ events in our system. Together, we will look at how to use event sourcing on top of Azure Functions with custom bindings, Azure Storage, and Azure EventGrid.
https://futuretech.nl/sessions/all-sessions-serverless-eventsourcing-for-pennies-using-azure-functions-storage-and-eventgrid/
As developers, we store our code in a system (GIT) that allows us to time travel, compare, work together, and reason about our code. We can go back in time to learn who made a particular change, where a bug originated, or which parts of our code have a high change rate. It stores our data/code’s evolution, a proven and valuable practice compared to just keeping the latest state on disk.
Still, as soon as we start building systems ourselves, we (mostly) model our system ‘as if’ we would store code on disk; we only keep the latest state, model it in the way we seem fit at that moment in time, and make it, so it fits in our relational database.
This session will explore the ideas behind event sourcing, a way to store and keep the evolution of data/ events in our system. Together, we will look at how to use event sourcing on top of Azure Functions with custom bindings, Azure Storage, and Azure EventGrid.
https://futuretech.nl/sessions/all-sessions-serverless-eventsourcing-for-pennies-using-azure-functions-storage-and-eventgrid/
Jan 29, 2021
Spoke at a conference
Serverless EventSourcing for pennies using Azure Functions, Storage, and EventGrid
As developers, we store our code in a system (GIT) that allows us to time travel, compare, work together, and reason about our code. We can go back in time to learn who made a particular change, where a bug originated, or which parts of our code have a high change rate. It stores our data/code's evolution, a proven and valuable practice compared to just keeping the latest state on disk.
Still, as soon as we start building systems ourselves, we (mostly) model our system 'as if' we would store code on disk; we only keep the latest state, model it in the way we seem fit at that moment in time, and make it, so it fits in our relational database.
This session will explore the ideas behind event sourcing, a way to store and keep the evolution of data/ events in our system. Together, we will look at how to use event sourcing on top of Azure Functions with custom bindings, Azure Storage, and Azure EventGrid.
https://www.azurelowlands.com/
As developers, we store our code in a system (GIT) that allows us to time travel, compare, work together, and reason about our code. We can go back in time to learn who made a particular change, where a bug originated, or which parts of our code have a high change rate. It stores our data/code's evolution, a proven and valuable practice compared to just keeping the latest state on disk.
Still, as soon as we start building systems ourselves, we (mostly) model our system 'as if' we would store code on disk; we only keep the latest state, model it in the way we seem fit at that moment in time, and make it, so it fits in our relational database.
This session will explore the ideas behind event sourcing, a way to store and keep the evolution of data/ events in our system. Together, we will look at how to use event sourcing on top of Azure Functions with custom bindings, Azure Storage, and Azure EventGrid.
https://www.azurelowlands.com/
2020
Loading...