Which projects are definitely worth writing on Serverless and microservices, and which ones are definitely not?

Question

Software design

Give examples of projects for which it makes no sense to use Serverless and microservices?

It is clear that there is no point for a ready-made monolithic project, for which the budget is allocated only for hosting and bug fixes.

And what about new projects?

It seems to me that the argument for here will be the answer to the question: is each calculation potentially profitable, i.e. Will the cost of processing each request be recouped?

In other words, with t.z. rational use of resources, it makes no sense to spin on microservices for an entertainment media project with free access, and vice versa, if access is paid, then why not?

Answer 1

It seems to me that the argument for here will be the answer to the question: is each calculation potentially profitable, i.e. Will the cost of processing each request be recouped?

This is present in any commercial project.
The answer, in my opinion, is "when it is convenient/profitable". Moreover, taking into account the costs of training programmers and devops, and the fact that maintaining / debugging Serverless and microservices is more difficult than "old and boring" technologies.

Answer 2

You can connect a third monitor via a USB adapter, it's inexpensive.
There is also an option to turn off the monitor built into the laptop directly from the Windows control panel. This is the simplest and most efficient option.

Answer 3

There are no such tricks with the BIOS in laptops, since all connectors cling to the integrated video card (with rare exceptions in the form of expensive mux-chips and the absence of an integrated video card as such).
List of CPU/GPU/Intel chipsets supporting 3 monitors