![]() Of course, finding useful abstractions in the code itself is hard work (but fun work). You’ll find 11 out of 10 of them would rather take over many simpler classes and modules than a single class or module that does everything. Ask any developer who has experience writing code and tests. Narrowly focused code is easier to write, maintain, and test. ![]() This benefit extends itself to testing as well, unit testing specifically. We can spend less time wrestling with where code should live at the level of frontend or backend because we have a simple to set of heuristics that make it clear: frontend with this and backend with that. The frontend and backend separation is not a panacea, but at one level it helps encourage of developers to do the right thing. Or, maybe it’s related to the user experience and how users interact with an application’s UI? When this is true then it will find itself right at home in the frontend. Is it related to the authoritative source of saving or providing information, or of implementing business rules or validation? When yes then the backend provides a cozy fit. One of those is that it’s easier to determine where code should live. The backend server still exists but it’s focus is becoming narrower. Nowadays, it’s a lot more common to find frontend frameworks being used to build a separate frontend application. Server-side code would generate and spit out HTML and JavaScript to a user’s browser. Waaaaaaaay back in the day the norm was to use backend technologies to develop both the backend and frontend. Web applications always have a backend and a frontend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |