2

My argument is frontend doesn't care which database backend is using. Sorry, but that is actually an argument for checking of the existence of IDs. The database backend is an abstraction which tends to be leaky - it does not matter how much effort you invest to make your frontend DB agnostic, there is always something which behaves differently when you ...


2

In short Yes and no ! Yes you can model it ! The UML activity diagram models control flow and object flow. Both are very practical to model individual functions, function composition and function pipelines: Functions would be represented by actions. Composition can be shown with activitiy edges, if needed using pins to show that object flows from the ...


1

Unfortunately, there is no one size fits all answer. Monkey patching is not generally a good idea as it places logic in places people don't think to look, especially new people who are looking at the API docs and trying to figure out where the split method is. However, there could be a very good reason to do it. For example if you think you're going to use ...


1

In general, you are correct. The back end should be abstracting the detail of the database away. We've switched databases twice without the front end even knowing. If you need a list of hotels with ids, the back end should provide a way to query only hotels with ids, regardless of what database is in use. Expecting the front end to filter a table is error ...


Only top voted, non community-wiki answers of a minimum length are eligible