OO design choice and single responsibility principle
I’m currently refactoring an application which periodically downloads content from various sources (http, ftp, sql, etc). There is a schedule which controls the times during which the application can be active. For example, it can download content between 8AM and 16PM. The application has been written in an object oriented language (C#).
OO design choice and single responsibility principle
I’m currently refactoring an application which periodically downloads content from various sources (http, ftp, sql, etc). There is a schedule which controls the times during which the application can be active. For example, it can download content between 8AM and 16PM. The application has been written in an object oriented language (C#).
Inventory Management System Design Problem “Items Packages”
I am developing a retail management system with inventory management module, I am facing a logic design problem and I don’t really know how to address the problem in an easy way, so I wrote an example which illustrates that problem:
Can this argument be enough?
We have two C++ classes named Important and Small
Can this argument be enough?
We have two C++ classes named Important and Small
Can this argument be enough?
We have two C++ classes named Important and Small
Can this argument be enough?
We have two C++ classes named Important and Small
Can this argument be enough?
We have two C++ classes named Important and Small
Performance of One API vs Multiple API’s
I was having a conversation with a colleague and although my opinion makes sense to me, I wasn’t able to back it up. I’m in the process of creating an API that will be hit hundreds of thousands of times per day. It’s fairly simple, and will just be doing some inserts into a relational database. There are essentially 3 functions I would need to create. The question is, what would have better performance, creating one API with different controllers (using .NET Web API or NodeJS something like that) or 3 different API’s.
Performance of One API vs Multiple API’s
I was having a conversation with a colleague and although my opinion makes sense to me, I wasn’t able to back it up. I’m in the process of creating an API that will be hit hundreds of thousands of times per day. It’s fairly simple, and will just be doing some inserts into a relational database. There are essentially 3 functions I would need to create. The question is, what would have better performance, creating one API with different controllers (using .NET Web API or NodeJS something like that) or 3 different API’s.