{"id":34734,"date":"2019-10-31T22:00:06","date_gmt":"2019-10-31T19:00:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/sravnenie-i-vybor-sistem-migratsii-dannyh\/"},"modified":"2019-10-31T22:00:06","modified_gmt":"2019-10-31T19:00:06","slug":"sravnenie-i-vybor-sistem-migratsii-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/sravnenie-i-vybor-sistem-migratsii-dannyh","title":{"rendered":"Krahasimi dhe zgjedhja e sistemeve t\u00eb migrimit t\u00eb t\u00eb dh\u00ebnave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Krahasimi dhe zgjedhja e sistemeve t\u00eb migrimit t\u00eb t\u00eb dh\u00ebnave<\/h2>\n

\n\"Krahasimi
\n
\nModeli i t\u00eb dh\u00ebnave gjat\u00eb procesit t\u00eb zhvillimit ka tendenc\u00ebn t\u00eb ndryshoj\u00eb, dhe n\u00eb nj\u00eb moment ai nuk p\u00ebrputhet m\u00eb me baz\u00ebn e t\u00eb dh\u00ebnave. Sigurisht, baza e t\u00eb dh\u00ebnave mund t\u00eb fshihet, dhe pastaj ORM do t\u00eb krijoj\u00eb nj\u00eb version t\u00eb ri, i cili do t\u00eb korrespondonte me modelin, por nj\u00eb procedur\u00eb e till\u00eb do t\u00eb \u00e7onte n\u00eb humbjen e t\u00eb dh\u00ebnave ekzistuese. Pra, funksioni i sistemit t\u00eb migrimit \u00ebsht\u00eb q\u00eb, si rezultat i ndryshimeve t\u00eb skem\u00ebs, ta sinkronizoj\u00eb at\u00eb me modelin e t\u00eb dh\u00ebnave n\u00eb aplikacion pa humbur t\u00eb dh\u00ebnat ekzistuese.<\/p>\n

N\u00eb k\u00ebt\u00eb artikull, d\u00ebshirojm\u00eb t\u00eb shqyrtojm\u00eb mjetet e ndryshme p\u00ebr menaxhimin e migrimeve t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave. Shpresojm\u00eb q\u00eb ky p\u00ebrmbledhje t\u00eb jet\u00eb e dobishme p\u00ebr zhvilluesit q\u00eb p\u00ebrballen me nj\u00eb zgjedhje t\u00eb till\u00eb.
\n<\/a><\/noindex><\/p>\n

Detyra<\/h3>\n

\nN\u00eb kompanin\u00eb ton\u00eb tani po zhvillohet aktivisht gjenerata e ardhshme e produktit \u2013 Docs Security Suite (DSS). Pjesa server po shkruhet n\u00eb .Net Core, dhe si DB p\u00ebrdoret Entity Framework Core. Gjat\u00eb projektimit t\u00eb aplikacionit, ne p\u00ebrdorim qasjen Code First.<\/p>\n

Modeli dominal i aplikacionit krijohet nga disa zhvillues n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb \u2013 secili \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr pjes\u00ebn logjike t\u00eb sistemit. <\/p>\n

N\u00eb gjenerat\u00ebn e kaluar t\u00eb DSS, sistemi i menaxhimit t\u00eb migrimeve p\u00ebrdorte klasiken Entity Framework Migrations (EF 6). Megjithat\u00eb, p\u00ebr t\u00eb \u00ebsht\u00eb ngritur disa pretendime, kryesore prej t\u00eb cilave ishte se n\u00eb EF mungonte nj\u00eb qasje e arsyeshme p\u00ebr zgjidhjen e konflikteve t\u00eb versioneve. Ky fakt na shqet\u00ebson ende gjat\u00eb rregullimeve t\u00eb defekteve n\u00eb kuad\u00ebr t\u00eb mb\u00ebshtetjes, prandaj u mor vendim t\u00eb shqyrtohen mund\u00ebsi alternative.<\/p>\n

Si rezultat i diskutimeve, u formuluan k\u00ebto k\u00ebrkesa p\u00ebr sistemin e menaxhimit t\u00eb migrimeve:<\/p>\n

    \n
  1. Mb\u00ebshtetje p\u00ebr sisteme t\u00eb ndryshme DB. P\u00ebrve\u00e7 MS SQL Server, PostgreSQL, Oracle, por potencialisht \u00ebsht\u00eb e mundur t\u00eb p\u00ebrdoren edhe t\u00eb tjera.<\/li>\n
  2. Puna me ORM. Fillimisht \u00ebsht\u00eb parashikuar p\u00ebrdorimi i EF Core, megjithat\u00eb n\u00eb faz\u00ebn e projektimit ishin t\u00eb gatsh\u00ebm t\u00eb shqyrtonin edhe ORM t\u00eb tjera.<\/li>\n
  3. Autogenerimi i migrimeve. Duke marr\u00eb parasysh zhvillimin Code First, d\u00ebshirohej t\u00eb shmangej nevoja p\u00ebr t\u00eb \"shkruar me dor\u00eb\" migrimet.<\/li>\n
  4. Konfliktet e versioneve. N\u00eb kushte zhvillimi t\u00eb shp\u00ebrndar\u00eb, gjat\u00eb bashkimit, EF Core mund t\u00eb bjer\u00eb p\u00ebr shkak t\u00eb konflikteve. Kjo b\u00ebhet nj\u00eb problem i r\u00ebnd\u00ebsish\u00ebm, pasi pjes\u00eb t\u00eb ndryshme t\u00eb aplikacionit krijohen nga zhvillues t\u00eb ndrysh\u00ebm, k\u00ebshtu q\u00eb duhet t\u00eb shpenzohet shum\u00eb koh\u00eb p\u00ebr secilin.<\/li>\n
  5. Dokumentacion dhe mb\u00ebshtetje e p\u00ebrparuar. K\u00ebtu, na duket se sqarimet nuk jan\u00eb t\u00eb nevojshme<\/li>\n
  6. Fal\u00ebsia. Kritereja \u00ebsht\u00eb relative, sepse nuk jemi p\u00ebrjashtuar nga bisedat rreth sistemeve jo shum\u00eb t\u00eb shtrenjta ose t\u00eb shtrenjta, por perfekte n\u00eb komoditet<\/li>\n<\/ol>\n

    \nSi rezultat i nj\u00eb studimi t\u00eb vog\u00ebl, jan\u00eb gjetur dhe pranuar p\u00ebr t'u shqyrtuar variantet e m\u00ebposhtme:<\/p>\n

      \n
    1. EF Core Migrations<\/li>\n
    2. DBup<\/li>\n
    3. RoundhousE<\/li>\n
    4. ThinkingHome.Migrator<\/li>\n
    5. Fluent Migrator <\/li>\n<\/ol>\n

      <\/p>\n

      Tani pak m\u00eb n\u00eb detaje<\/h3>\n

      \n\"Krahasimi
      \n      EntityFramework Core Migrations<\/a><\/noindex><\/b><\/p>\n

      Natyrisht, ky ishte opsioni i par\u00eb dhe kryesor p\u00ebr zgjedhje. Nj\u00eb mjet natyror, q\u00eb funksionon nga kutia pa ndonj\u00eb k\u00ebrkes\u00eb t\u00eb ve\u00e7ant\u00eb. Nj\u00eb sasi e madhe dokumentacioni, si zyrtar ashtu edhe joaq zyrtar, thjesht\u00ebsia etj. Sidoqoft\u00eb, ankesat q\u00eb iu b\u00ebhen klasikes EF jan\u00eb gjithashtu t\u00eb vlefshme p\u00ebr EF Core. <\/p>\n

      Pra, p\u00ebr EF Core jan\u00eb identifikuar avantazhet:<\/p>\n