Creating system diagrams for a small app
I am learning system design (on my own) and still I am not clear on a few things. Assume there is a simple application with a front-end and a database for storing of the data.
In the system architecture diagram, will there be only two parts (UI and DB) or should I include some UI modules for calculations, for example? And what about hardware devices that the system is using?
Creating system diagrams for a small app
I am learning system design (on my own) and still I am not clear on a few things. Assume there is a simple application with a front-end and a database for storing of the data.
In the system architecture diagram, will there be only two parts (UI and DB) or should I include some UI modules for calculations, for example? And what about hardware devices that the system is using?
Architecture for application-wide diagnostic-gathering tool?
My product owner wants us to report more information on the state of the product when a user contacts customer service through an in-app form. The form eventually results in an email being sent to a customer service email list and handled elsewhere.
Architecture for application-wide diagnostic-gathering tool?
My product owner wants us to report more information on the state of the product when a user contacts customer service through an in-app form. The form eventually results in an email being sent to a customer service email list and handled elsewhere.
Is there anything inherently bad about mixing paradigms in an application?
I am currently in the process of writing a (custom) Minecraft server application in C#. I figured it’s a good way to teach me a lot of important things like concurrency and especially memory efficiency (due to simply the vastness of the object space in Minecraft).
Is there anything inherently bad about mixing paradigms in an application?
I am currently in the process of writing a (custom) Minecraft server application in C#. I figured it’s a good way to teach me a lot of important things like concurrency and especially memory efficiency (due to simply the vastness of the object space in Minecraft).
Long running task initiated in the web site
The plan is to develop generic solution for long running task initiated in web site by users such as:
1. upload large file and do some custom processing and then insert in the database.
2. export large amount of data
How do you make a service stateless?
When doing Domain Driven Design it is advised that services should be stateless. There are several kinds of services when doing DDD:
Architecture for dashboard
I’d like to know if my Architecture idea, is the best approach following some pattern.
Architecture for dashboard
I’d like to know if my Architecture idea, is the best approach following some pattern.