The difference between frameworks and libraries

NOTE: I didn’t google definition either for ‘library’ nor for ‘framework’ for years. I even didn’t read Wikipedia articles during the last 3-5 years. That means that thoughts are my own, so you could disagree with me.

For me, the difference between a library and a framework is in architecture freedom.

A framework provides you a skeleton for your project with some basic architecture. It would be a low-level architecture like ‘how to work with IO’ or a high-level MVC implementation. Each framework provides you a very limited number of solutions for a particular problem. It benefits you in a good structure for each project based on the chosen framework. If you do not with a proposed way to follow, in most cases it leads to a pretty hacky and complicated solution.

On the other hand, the library gives you much more freedom. You can choose an architecture which fits best your needs. It just provides some APIs which you can use as you want. It means any project with some library will be different from the previous one.

Sometimes it’s useful to build a framework on top of the library to use it. There are a lot of good examples. You can build your own framework based on existing too. Both of these ways have own pros and cons like any tool you use.

No conclusion from me this time. I just need some link with these definitions to be able to share them.


.net .net-framework .net-framework-3.5 agile ajax ajax-control-toolkit ampq ansible apache automation axum babel bash benchmark blog blog-engine bootstrap buildout c# cache centos chrome ci cinder ckan cli cloud code-review codeplex community config debugger deface dependencies development-environment devices devstack devtime disks django dlr dns docker dockerimage dos easy_install elmah encoding environment-variables error event events everything-as-a-code exception exceptions fabrik firefox flask foreach forms fstab gae gcc gerrit git github go google google-app-engine grep hack hacked hardware headless horizon hound html hugo iaas ienumerable iis internet iptables iron-python ironic iscsi java-script javascript jenkins jquery js jsx k8s kharkivpy kiss kombu kubernetes kvm kyiv lettuce libvirt linux lio loci logging loopback losetup lvm mac-os macos mercurial microsoft microsoft-sync-framework mobile mono ms-office msbuild networking news nginx npm npx offtopic oop open-source open-xml opensource openstack openvswitch os packages paraller-development patterns-practices performance php pika pip plugins pnp podcast popup postgresql profiler project protocols proxy pycamp pycharm pycon pykyiv pylint pypi python python-3 qcow quantum qumy rabbitmq rar react reactjs refactoring rfc rhel search-engine security selenium server shell silverlight socket software-engineering source-control sourcegear-vault sources sql sql-server sql-server-express sqlalchemy ssh static-site sublimetext svg tests tgt tipfy todo tornado typescript uapycon ui uneta unit-tests upgrades usability vim virtualenv visual-studio vitrage vm vue.js vuejs web-development web-server web-service web_root webpack webroot windows windows-live word-press x32 x64 xcode xml xss xvfb интернет-магазин книги

Recent posts

Go 1.18: new features

Всё будет Kubernetes

2022 Relaunch

Everyday Blogging

I don't want this CI


2022 (3)
2019 (73)
2018 (2)
2017 (3)
2016 (2)
2015 (3)
2014 (5)
2013 (17)
2012 (22)
2011 (36)
2010 (25)
2009 (35)
2008 (32)
2007 (2)