Framework · Library
Framework / Library
What is a framework?
- Library = a toolbox you pull from
- Framework = the structure and skeleton of an application
- Don’t reinvent the wheel
What this concept really changes is not the code but how you read schedules and quotes. Features that have been proven tens of thousands of times, such as login, file upload, table sorting, and charts, are taken off the shelf, and only the parts that contain your company's own business rules are built in-house. That lets you ask why the '4 months' in a development quote is 4 months, and which items could be shortened by using existing tools. The line between what you build and what you borrow is the cost line.
The real dividing line is 'who calls whom.' You call a library when you need it. With a framework, you slot your code into designated places and the framework calls it for you. This is known as inversion of control. That is why you can swap out a chart library midway, while changing a framework is effectively a rebuild. An SDK, for comparison, is a bundle of tools for connecting a specific company's service, such as Kakao or Toss, and an API is a gateway for exchanging data with the outside, so they sit at a different level.
What to check when choosing is surprisingly simple: whether it has been updated in the last 6 months, whether weekly downloads are steady, whether the docs have enough examples, and whether the license allows commercial use. For maintenance, the one your team already knows beats the one with the flashier features.
The point where things most often break in practice is the assumption that 'once it's attached, it's done.' Libraries get new versions, and one that was trendy three years ago may now have no maintainer. A single update can break the screen or trigger a security vulnerability notice. It is not rare for a library recommended by AI to not actually exist or to be already deprecated, so check before installing. A library you assumed was free may turn out to carry a license that requires you to disclose your source code, and companies really do get asked to publish their internal system code.
Seungtae ParkHands-on AX instructor who teaches AI business development and marketing automation by building real systems
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”Libraries for code reuse have existed since the early days of software. Frameworks, which provide an application’s structure, grew out of the push to improve reusability and productivity.
Consider a hypothetical case. Company A, an auto-parts maker with 90 employees, had been tracking defect data by production line across 12 Excel sheets. Month-end reporting alone took two staff members a full three days, and an outsourced development quote came back at KRW 38 million (≈ US$28,400) and 4 months. Kim, a manager on the production engineering team, volunteered to build a dashboard in-house within 8 weeks.
- After Manager Kim uploaded two A4 pages of requirements, the AI came back first with a design proposal: 'build the screen structure with the Next.js framework and add a chart library for the graphs.'
- Manager Kim decided to build only the defect-judgment criteria table for each line in-house and left login, Excel upload, and table sorting to existing libraries. Two weeks of work shrank to two days.
- Park, an assistant manager on the IT team, compared two chart libraries. One was last updated 14 months ago, the other 11 days ago. Saying 'let's go with the one that has Korean examples in its docs,' Park picked the second.
- One Excel-conversion library recommended by AI failed at installation. On inspection, it turned out to be a package abandoned two years ago, and swapping in a replacement took half a day.
- In week 7 it went onto the company server, and the month-end tally time dropped from three days to 40 minutes. Only about 15% of the code was written by hand, and tool costs were KRW 0 (≈ US$1) because everything used free licenses.