Performance

Today we came across an interesting issue at work: we have two teams A and B who interchange API calls. Team A needed an API from team B to process a business that is owned by team B of course. The signature was like the following: public OutputEntity MyMethod(List listOfIds); It appeared afterward that this method was very slow, and the client was already very upset about the low performance, which consequently caused big pressure on the teams by the superiors to enhance the performance. After investigating the issue, it appeared that the list of ID’s sent as input consists of some ID’s that do not need to be processed, this criteria of “not need to be processed” is a business owned by team B, done by using properties of the entities these ID’s represent. So the solution to this issue was one of the following: ...

In one of the modules I am working on, my unit tests used to take tremendous amount of time (4 minutes per test 🤢. I inherited the NHibernate config file from previous NHibernate test module that was used somewhere before! At the beginning I thought that this is something common when you use NHibernate with rich applications, so I didn’t pay much attention, but then it became a real headache. ...