Go meetup #18

Hosted by Pure Storage

Please note at the Pure Storage office, all meetup attendees will be required to sign a generic NDA used for all office visitors to be able to attend the meetup.
Doors are open from 17:30, talks will start 18:00, and we have 3 talks.

1. Vilibald Wanča (Pure Storage), Introduction to Cell-Based Architecture

2. Miłosz Smółka, Killing the legacy and other CQRS stories
Do you know the feeling when your project gets stuck, and you can’t move forward? You see a few ways out, but all seem equally bad. You start wondering if the project is doomed or if you just miss some special knowledge. I felt this the most while trying to move out of legacy systems, but it’s common in many projects.
Over time, I learned that changing your mental model may reveal a solution you didn’t see before. Looking back at some of my projects, I realized one of the patterns that helped me think differently was CQRS.It doesn’t matter if you’ve used CQRS before, as I don’t plan to bore you with abstract definitions. A lot has been said about the theory of CQRS. Instead, I want to show how I used it in practice. I will share three real stories from different companies and projects where I managed to move forward and better grasp CQRS. One of them was the most challenging: killing the legacy codebase.

Bio: Miłosz Smółka writes about Go, modern business software, and related topics at https://threedots.tech. He enjoys sharing what he has learned while working at startups and building products in different fields.

3. Robert Laszczak, Rethinking Domain-Driven Design in Go: From Myths to Reduced Project Complexity
Splitting problems into smaller ones can be a good strategy for tackling complex problems. But sometimes, instead of making project development faster, the opposite happens. Ultimately, developing the simplest feature requires the heroic work of 10 teams on a dozen microservices over half a year. Sounds familiar?
"Divide and rule" is not the only strategy that we can implement in complex projects. One of the most established approaches that can simplify implementing functionalities with complex domain logic is Domain-Driven Design (DDD).
I found DDD very useful in multiple projects with complex domains that I could work on. On the other side, I know that people believe in many myths about DDD used in Go. Most of them are sourced from using DDD in projects that don't require such a sophisticated approach or from projects implemented by people who didn't understand the principles of DDD.
During this talk, I will demystify DDD and give you a real-life example of where empowering DDD helped simplify them and increase development velocity.
If you don't work on a project with complex domain logic now, this presentation may still be helpful for you if you want to work on more challenging projects in the future. I will also give you some hints on which parts of DDD you should start from and what techniques work with DDD well.

Bio: I'm blogging at threedots.tech. Author of "Go With The Domain" and Watermill.io.
My programming journey spans 16 years, during which I've navigated diverse domains, including infrastructure, global financial platforms, and security. A couple of years ago, I finally found a language I loved: Go.