Hi David, I think the answer really depends on number of things:
- How much growth you expect, in terms of concurrent users/processes and data file size, over the next 3-5 years. - How is your application expected to change over then next 3 - 5 years. - What kind of IT support you have. - What does your application do? Is it all internal facing using 4D Client? Does it have Web Clients? Does it connect to other internal and external systems? If you have mostly MacOS IT support and experience, and you expect modest growth in your user base and application in the future, and your app is currently performing well, it’s an easy decision to get another Mac Mini (maybe with more RAM). If you expect to double (or more) your users and data and expand your applications capabilities, and your current system performance is mediocre, and you have some Windows IT support, you could consider getting a Windows server. I’m assuming your existing system has sufficient redundancy to meet the requirements of your corporate Disaster Recovery Plan. And one more thing. If you buy a new MacOS machine today you will likely have to run 64bit, which means your app needs to be 64bit compatible. If it’s not already 64bit compatible, that may be considerable work, depending on the nature of your app. HTH, Tom Benedict > On Sep 11, 2020, at 13:08, David Loeppky via 4D_Tech <[email protected]> > wrote: > > I'm ready to upgrade our 4D server machine and would welcome any insights > and recommendations. > > Some details: > - 40 Users (Mac and Windows) > - 4GB data file > - 120 tables > - The current server is a 2011 Mac Mini with 8GB and raid 4XSSD HD > > Questions about the new server: > - Windows or Mac? > - Recommended features. > > Many thanks for the input. > > -- > > Regards, > > David Loeppky > ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
