All geek questions in one place

Corp IT Systems. Invest in A or B?

It is rather a general question about which direction would be the best investment for the company.

The main application of our company is written in Visual FoxPro and is about 9+ years old. The database is a huge 15+ gigs, and the basic logic is complex and, even worse, the data model is terrible. The two guys who built it and supported it all these years, at least in the 50s, so there’s no need to say that retirement or possibly death can occur within the next decade or so.

This VFP application manages all our core business functions and requires Terminal Services and Citrix to access it from the outside world. Our web applications must interact with it through ODBC, and we always have performance issues. The servers that run this system are also very old, such as a Win 2000 server and are falling apart.

We recently held meetings to update the systems that run this main application, as well as other services such as email and file storage. However, the biggest expenses are the purchase of new server hardware, OS licensing, terminal services licensing, Citrix licensing, etc., to solve some of the performance and external access issues that we now have, as well as generally bringing us into our systems.

Price will range from $ 55K to $ 65K. So, as a web developer, my point is that it is a huge waste of money! My solution was to invest that money in rewriting the base system to work on the .NET web platform. This would eliminate the need for licensing Terminal Server and Citrix along with expensive hardware and configuration management to run it. I see no reason to invest such money in an outdated system, which in any case should be on it.

, . , -, , . , -, , . , , , .

+3
10

. 60 000 10 , () , , .

, 50 000 . , - , 60 . . , .

- , -, ( , ..) . , ; - .

S.Lott , , , . , - , , FoxPro, (, "", " " )...

: .NET( ) Delphi. . , "". , , .

, , - , - - "" . , Delphi / ; "delphi" SO 3340. SO - :

  • c# - 57293
  • .net - 30577
  • asp.net - 26600
  • java - 31023
  • vb.net - 5996
  • delphi - 3340
  • foxpro - 69
  • vfp - 27

. Delphi, , 10% #, non-techies . Foxpro/VFP 1%. , , :

  • , () ?
  • / ?
  • , ? ( )
  • , ? ? ?
  • ?

--, , , , , , . FoxPro . FoxPro COBOL; , , , , FoxPro? , . VB6 , VB/Access FoxPro .

, , , , , . , . , , , FoxPro? ​​? ? , 20 , , , - , .

+3

. , . , , .

ROI. , $100K , , - . .

" ". , . , .

: " ?" ", ?" $- .

, , , , , , , , .. ..

" ". , .

( 50 , . . 80 , , .)

( ) .

, -, .

, , -. , , , .

+6

, , - , , , , .

, , , , .

+1

, , , :

  • , , .

  • , . , , , .

  • . , . ?

  • . -.

  • .. . ? Visual Studio ?

  • . , . 300 000 , , 3 , , , , , .

  • . . . , - , .

  • . - . , , ( , ).

  • -. , , , ,

+1

:

  • "FoxPro", "Craigslist" -: 2.
  • ".NET", Craigslist - : 252.

, , . , , , , - , , , .

, , sup1; , . ( 10 , .NET - , :)

[1] , . , . , ( , ).

+1

VFP ( 20yrs Foxpro/VFP STILL , / VFP ), . , .Net, - .Net , . , // PITA.

, ... VFP, VB, Access . , , , / , , . , , , , , , . VFP .Net .

, VFP, .Net , BOTH. , .

+1

, ROI - , .

0

JOS - " - , ".

, , . , , .

:)

0

,

  • .

  • .

  • Foxpro, .

.

0

There is no magic bullet for the company. The only way to make sure you are on a new server is to take advantage of the stability and speed that existing business critical software brings. Then, once it's parked for several years, start remodeling the thing on another platform, such as .NET, if that's what you want to do. Whereas, you will have to transfer the VFP data to the new database structure at some point.

0
source

Source: https://habr.com/ru/post/1728219/

More articles:


All Articles