When I joined the company, the lack of computer resources was a chronic problem.

Efficient use of memory was the biggest challenge, as creating a three-digit two-dimensional array alone would not allow the program to run.

At work, I was fighting for workstations.

However, PCs no longer face this problem as they now have ample resources.

With the advent of programming languages (such as Go) that are strong in concurrency processing, objects of the order of one million can now be handled as usual.

However, I should not be reckless.

"pq: sorry, too many clients already"

I have tried various responses to the database screams, but when I checked the resource manager, I found that the disk (write) usage was over 99%.

Well, I thought, writing 100 agents' information 30 times per second to a database created in docker, the database would scream.

I have been living without resource shortage problems for more than a decade, so I guess I did not realize how reckless I was.

-----

I was having a conversation with my wife.

Ebata: "My database went down..."

Wife: "What! That's an accident! Are you okay?"

We were both nodding our heads like 'What are you talking about?'

What the general public associates with the word "database" would be an administrative management system, an electricity delivery system, or an e-commerce system such as Amazon.

If that type of database were to go down, it would have an enormous impact on social life.

In my wife's mind, 'a small experimental database that I created locally just for my own programs' is not included in the database.

I think that is the feeling of ordinal persons.