Long wait for common .Net lib to get build by another team

shalini Pahwa
2 min readMar 26, 2024

Its long wait to get one library that we need to use in all current application that we are building.

It has common component like caching, db connectivity, API call with several authentication and authorization mechanisms and other common components.

Why I am discussing about all this?

  1. 4–5 projects that are currently built, need upgrade once the library is available. And some are in development stage.
  2. There is development cost involved to upgrade those projects.
  3. Most of them not using all the features provided by that library.
  4. We are bound to use .net framework to use that existing library for new projects. Although .net 8 has cool features.
  5. We are creating tech debt.

I saw there are 4–5 projects built with deprecated library. As new Library still not built.

I know it has several features but why not release the library feature wise?

Creating the big component takes time to develop.

Whenever we have bigger problem, we use to break it in smaller chunks and resolve it. That's why microservices are popular now-a-days.

--

--