In the real world, 'business logic' is sometimes mixed with 'business rules'. The examples and definition I've given are with respect to how the term is used in real life and may not exactly match the textbook definition.
The "business logic" is actually the most important part of your code. As a software developer, your task is to translate them into code using your technical skills. That is no easy task. You sometimes have to stop thinking in coding terms. That is the challenge that distinguishes a junior developer from an experienced developer who are confident in the tech and spends most of his or her time instantly translating these rules. It is all about the big vs the small picture. When you know how to confidently write and structure code and can focus more on business concerns independent from details in code.
Thanks for the video. The most difficult part is to differentiate business logic from other types of logic and other parts of your system. There is UI layer, protocol/communications, application, security, storage, caching, validation... You have taken the original cargo shipping as an example, from the blue book, which is nice since it is a very valid model for learning purposes. I found two terms in your video that are not really part of the domain - first is data (what is data in the context of business?). The second one is representation - what is representation?
Hi Nova, Absolutely it can be explained with diagrams. In fact, one of the most common ways to demonstrate business logic is through flow diagrams that guide the user through the experience.
Hmmm strange that this specific example is very similar to the one given by Eric Evans when talking about domain driven design. Check the talk in the link below (Hint: increase playback speed): ruclips.net/video/pMuiVlnGqjk/видео.html
In the real world, 'business logic' is sometimes mixed with 'business rules'. The examples and definition I've given are with respect to how the term is used in real life and may not exactly match the textbook definition.
Thank you for this. The phrase "business logic" is thrown around so much without anyone ever explaining what it means.
The "business logic" is actually the most important part of your code. As a software developer, your task is to translate them into code using your technical skills. That is no easy task. You sometimes have to stop thinking in coding terms. That is the challenge that distinguishes a junior developer from an experienced developer who are confident in the tech and spends most of his or her time instantly translating these rules. It is all about the big vs the small picture. When you know how to confidently write and structure code and can focus more on business concerns independent from details in code.
Thanks for the video.
The most difficult part is to differentiate business logic from other types of logic and other parts of your system. There is UI layer, protocol/communications, application, security, storage, caching, validation... You have taken the original cargo shipping as an example, from the blue book, which is nice since it is a very valid model for learning purposes. I found two terms in your video that are not really part of the domain - first is data (what is data in the context of business?). The second one is representation - what is representation?
Thank you!
You're welcome!
Woww simply won...
Super simple and strigh to the point explaination, thanks!
You're very welcome!
How do you put business logic into a document? Can it be explained with diagrams?
Hi Nova,
Absolutely it can be explained with diagrams. In fact, one of the most common ways to demonstrate business logic is through flow diagrams that guide the user through the experience.
So MVC MVVM VIPER , we should put business logic in Model / Entity
Hmmm strange that this specific example is very similar to the one given by Eric Evans when talking about domain driven design. Check the talk in the link below (Hint: increase playback speed):
ruclips.net/video/pMuiVlnGqjk/видео.html
I think I made this video right after reading Eric's DDD book !
Thanks a lot bro
Happy to help
Thank you!
You're welcome!