Assigning responsibility for cancelling an Order
During a conversation with our Domain Expert we can across this feature:
Implementing multiple tables for the same entity due to processing power on Client apps
I reached a design/architectural issue on the large application I’m working on, at the point of writing possibles solutions on a chalkboard. Our product consist of a client-server information system whose implementation was built on REST paradigms.
Managing non-domain application behaviour in CQRS
Here’s a scenario.
Which layer should service errors be handled in?
I am coding in a multitier architecture in Java, and I perform a query to a web service.
How to ensure the success of processes after a deadlock exception occurs?
No matter the programming language is and whatever the database is, the concept should be the same:
“Middle ground” architecture for client-server iOS apps?
I see two obvious approaches to the architecture for an iOS app which needs to talk to a server to do its job.
How often do you refactor or restructure your code in long term projects? [duplicate]
“WTH, I can’t believe I used to write code like this“
How often do you refactor or restructure your code in long term projects? [duplicate]
“WTH, I can’t believe I used to write code like this“
Where should the “not empty field” validation code be written on a 3-layer application?
When working with the 3-layer model, where should the validation code be placed? for: not empty fields, unchecked options, null values, wrong-written dates, etc.
Implementing a modern web application with Web API on top of old services
My company has many WCF services which may or may not be replaced in the near future. The old web application is written in WebForms and communicates straight with these services via SOAP and returns DataTables.