While i really enjoy reading your architecture document, i think it is a tony bit overengineered 😁. Dont get me wrong, working on complex architectures is a joy for me too, especially with queue and websocket related stuff 😍 But looking at your initial requirements, it should be obvious that you dont need all these, maybe accidental, complexity. You could all do this with a simple MVC for example, most likely it will serve your needs for the next two years. Keeping an eye on the code modularity should be all you need. Its hard to not use the technology you love, for the job it does not fit.
I really love this angular/vue/react and complex architecture stuff but i am often getting hit by simply not choosing the right tool for the right job, you know?
I dont know Go, but on my perspective a web framework like Spring boot, Bootstrap and postgres would did the job in one day - or? But after all its about what we love in doing, so if it is a side project, overengineer as much as you want 😍👌
I work as CPO for a Swiss Telco/Messaging Platform Company.
My real passion is developing in Golang, Vue-Nuxt/ReactJs/Angular with Redis, Nsq/RabbitMQ, ArangoDB, MongoDB and Sql
I work as CPO for a Swiss Telco/Messaging Platform Company.
My real passion is developing in Golang, Vue-Nuxt/ReactJs/Angular with Redis, Nsq/RabbitMQ, ArangoDB, MongoDB and Sql
Hi Niklas
So, yes, I agree, mostly.
But fullstackjob.com is just my first MVP of the underlying Board Engine I am building. And for this project there are some topics like scalability, multi-tenant, white-labeling where a bit more complex architecture is needed. To build just the board as it is now for sure nothing of all that or a graph is needed :-)
And yes, between us... a bit it's about loving doing new stuff.
But from my "day-job" I know about the need to control this part of myself. At the end everything needs to make sense :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While i really enjoy reading your architecture document, i think it is a tony bit overengineered 😁. Dont get me wrong, working on complex architectures is a joy for me too, especially with queue and websocket related stuff 😍 But looking at your initial requirements, it should be obvious that you dont need all these, maybe accidental, complexity. You could all do this with a simple MVC for example, most likely it will serve your needs for the next two years. Keeping an eye on the code modularity should be all you need. Its hard to not use the technology you love, for the job it does not fit.
I really love this angular/vue/react and complex architecture stuff but i am often getting hit by simply not choosing the right tool for the right job, you know?
I dont know Go, but on my perspective a web framework like Spring boot, Bootstrap and postgres would did the job in one day - or? But after all its about what we love in doing, so if it is a side project, overengineer as much as you want 😍👌
Agree, but ;-)
Will answer you tomorrow... On the street
Hi Niklas
So, yes, I agree, mostly.
But fullstackjob.com is just my first MVP of the underlying Board Engine I am building. And for this project there are some topics like scalability, multi-tenant, white-labeling where a bit more complex architecture is needed. To build just the board as it is now for sure nothing of all that or a graph is needed :-)
And yes, between us... a bit it's about loving doing new stuff.
But from my "day-job" I know about the need to control this part of myself. At the end everything needs to make sense :-)