For some products, having your own language that your customers can use to be productive, or make your product that much more powerful, is a Domain Specific Language. Think Atlassian’s Jira Query Language, Github’s filter feature etc.
So – after quite some time working with distributed systems, I want to share the decisions made throughout as you build an event-based distributed system.
I want to share some of the things that I’ve noticed, and my thoughts in general in these different approaches – what they look like, pros and cons etc.
At work, we deploy all applications as Docker containers via Kubernetes – I really like this way of delivering applications, running on one machine means it will work the same way (in theory) as in another machine. Why not do the same for my Hobby projects albeit a much more simplified way.
So, this weekend, I made my first attempt – what I wanted to achieve is a proof of concept,
.NET Coreapp talking to
MySQL, both of which being docker-ised. I also wanted to use Gitlab’s free CI for it’s simplicity as this is what I’m really after – don’t want to have to write a ton of scripts.
For one of my hobby projects, a server-side rendered React.js app using nextjs with asp.net core 2.2 serving the web API, I’ve made a conscious decision to keep all validation server-side only to reduce the effort required on the front-end side.
As for SPA being used for a hobby project, it’s great for learning, but not so much for speedy development… when will I ever learn – but that’s a story for another time.