Sander Vink
Technical Lead @ Infi Utrecht
Utrecht, The Netherlands
Actions
My name is Sander, I am 36 years old, happily married, father of two kids, and have been working in development for over 15 years.
Started out as a front-end developer, but have many years of back-end development experience as well now, and done my fair share of product owner work. Additionally I love to facilitate business people and users by organizing event storming and story mapping sessions.
Working as Technical Lead at Infi Utrecht. Board member and treasurer of Fronteers in my spare time.
Links
The importance of ubiquitous language
This is a practical talk around the importance of ubiquitous language. We all know (or should know) that this is important, and I will demonstrate this by showcasing a project I have been working on last year (built on/with Event Sourcing). I will explain the good efforts that were done to fulfill this, and also all the work that was undone by a single meeting of business people.
Using GitLab Pipelines for Auto-deployment
Back in the day people used (S)FTP to ‘deploy’ their code to production. Especially when working in teams this could have nasty side effects, like overwriting changes made by a team mate or losing a week’s worth of development by accident with a single ‘Save to FTP’-command. So everybody stopped using this, right?
Nowadays it is a lot more common to have some sort of versioning control in place (like Git or Subversion). This is quite an improvement to prevent losing changes (and having a backlog of changes), but you can do so much more!
In this talk I will show (and explain) how to use GitLab Pipelines to automatically build your code (where necessary), test your code, and deploy it to production. I have several examples:
- WordPress plugins deployment to a custom VPS
- Symfony 4 deployment to a custom VPS
- Deployment to Azure
- Deployment to Heroku
These will also show the difference between using FTP for deployment versus Git, which seems arbitrary, but can be a very big difference in terms of feedback you get in GitLab (which I will show for both).
CQRS & Event Sourcing with Prooph
Last year (2018) I worked on a project for which we thought Domain-Driven Design would be a perfect match, because we really needed to engage our users as early as possible during development. Additionally we had some technical requirements for which CQRS and Event Sourcing also seemed like a good match.
During this talk I will explain why we thought this was, how we implemented this with the help of Prooph components, what kind of problems we ran in to, and how we solved them.
My talk is divided into the following parts:
- Brief explanation of the project and its requirements on a functional level (what it should do, target audience, etc; non-commercial)
- Why we thought Domain-Driven Design would be a perfect match
- Brief explanation of CQRS and Event Sourcing
- Outline of the available Prooph components (what they are/do, and which ones we decided to use)
- Code examples (small) of how we implemented this in the project
- How it performed in the production environment, which problems/complexity we had to face, and how we solved that (mostly back-end, but also front-end)
This talk is aimed at Intermediate, but it can be turned into an Advanced talk by shortening the DDD, CQRS and Event Sourcing explanations, and showing more code of how we fixed the problems we faced. Additionally I can provide more details about the architecture that was used in production.
It is mainly focused on development in general, but also includes the following categories:
- APIs (REST)
- Databases
- Frameworks (we used Symfony 4 and Prooph combined)
- JavaScript
Sander Vink
Technical Lead @ Infi Utrecht
Utrecht, The Netherlands
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top