I didn’t get do you do integrations besides of your DB.
To me architecture sounds good anyway. I’m not GO dev but it looks like stack is your main problem not architecture itself. Multiple models is great long term approach which makes sure you are not leaking implementation details of your persistence/3rd party services to your client. You have layer of mappers where you can enrich model in optimal way and at the same time you can accommodate whatever client request/payload quirks you may need. Yes it’s sometimes annoying to add one field and pass it across all layers but it’s the price and software development is all about balance and compromises. I worked in projects that didn’t follow this architecture and any kind of change in DB/3rd party were cascading through entire application so end up changing hundreds of files instead of couple of models and few mappers
You may have issues with this architecture if you invoke services directly one from another for complex use cases. This can couple things together. If that’s what’s happening think if can apply Facade. Try using/reusing more trivial and focused services in Facade to make sure that for example Order service does not depend on Client service. Leave it to ClientOrderFacade.
I like (no) how everyone knows this is about everybody’s mental health but you can only push things these days if iT iS aBoUt cHilDrEn or other touchy topic. Apparently adults can’t have mental health issues I guess, otherwise how will they do their jobs for cents
What do you mean obsolete? People who buy new phone every year will buy new one regardless of is it iPhone or Android.
iPhones actually last longer, especially flagship models. My iPhone 5s (2013) was with me for 7 years and still in use by my relatives. It got around 6 years of iOS updates. Even my low-end iPhone SE (2 gen) from 2020 runs perfectly and still gets latest iOS.
But it doesn’t make sense. If I would have people which I like so much in the office would, you know, go to the office. If I don’t wonna go well… then I don’t like those people enough and there can’t be bonds anyway. We will just come, say hi, do job, go home. What a great creativity boost
First of all, what you are doing is integration via DB. Unless that was conscious, I would avoid using this approach. System is much easier to manage when DB/schema used at most by one app. You have two ways to achieve it, move towards micro-services or monolith. Yes monolith is still great for some use cases.
If we talking about your current system state every app should do changes in most backward compatible way. It worst cases it will lead to duplications. Let’s say if you want to change table X because there is such need for app A and at the same time app B uses this table. Instead of modifying X you create table Y that satisfies needs of A and make sure that data written into Y as well as into X to maintain B.
Rather, there are too many indifferent and/or supporters so no doubts that protests will be suppressed.
On the other hand, Russians show off a lot but when time comes to action they behave like pussies. Protests like „Let’s all be friends. War is bad”. What a joke. Look how brutal are French protests.
I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.
Not to mock you. My point is that methodology is not import when team consists from responsible professionals
I got narrative but isn’t Jan 7 is orthodox thing not Russia/soviet thing. I mean, I don’t care how people celebrate their imaginary friends but it just weird
It might be degraded comparing to default experience but it’s not like you are missing something that you have on other OS. I mean, you can’t iMessage on Linux, right?
I didn’t get do you do integrations besides of your DB.
To me architecture sounds good anyway. I’m not GO dev but it looks like stack is your main problem not architecture itself. Multiple models is great long term approach which makes sure you are not leaking implementation details of your persistence/3rd party services to your client. You have layer of mappers where you can enrich model in optimal way and at the same time you can accommodate whatever client request/payload quirks you may need. Yes it’s sometimes annoying to add one field and pass it across all layers but it’s the price and software development is all about balance and compromises. I worked in projects that didn’t follow this architecture and any kind of change in DB/3rd party were cascading through entire application so end up changing hundreds of files instead of couple of models and few mappers
You may have issues with this architecture if you invoke services directly one from another for complex use cases. This can couple things together. If that’s what’s happening think if can apply Facade. Try using/reusing more trivial and focused services in Facade to make sure that for example Order service does not depend on Client service. Leave it to ClientOrderFacade.