Lol. Android phones definitely have no security concerns. Any internet/Bluetooth capable device can be potentially compromised. Just use Nokia 3310
Top ten comments do not mention typo. What a hell is going on. It’s Lenuks, not Linux
Apple’s 2024 is most accurate. We are all pawns.
Try official example from JUnit team. https://github.com/junit-team/junit5-samples/tree/r5.10.2/junit5-jupiter-starter-maven
Then add jacoco plugin with prepare-agent goal
CMDR?
Please, can you give an example of such code snippets? I’m wondering what people consider reusable in different projects.
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.
Thank you. This actually gives perspective on radiation level better than Rads
It’s called replica :)
„GIA is just around the corner” - any IA startup CEO