GNU Make vs. VMware Cloud Director vs. VMware Cloud Foundation

GNU Make is a great tool for simple builds where language-specific options are not available, or to provide shortcuts for common commands (e.g., "make build" as shorthand for "go build ..." with a bunch of flags). However, it is complementary to other build systems. It does not replace them, which is perhaps one of its greatest strengths as well (works with existing ecosystem instead of trying to do everything). GMU Make it simple to get started with, and the philosophy of understanding how sources map to outputs, as well as the dependency graph, are beneficial.

Incentivized

If you have a lot of customers that all need to have a separate place to work in, without the possibility of getting in each other way, and you want to safe yourself a lot of work. Than I strongly recommend you Cloud director. Ofcourse, only if you have a VMware environment as your working environment. If you just have a small group of customers and you can easily handle the work that's coming from it, then it is overkill to add cloud director to your environment. In a later station, you can always introduce cloud director (so tis never to late if you still want to use it)

Incentivized

It is best suited for an on-premise cloud solution where customer can shift their entire production environment. Also, the customer has a preference for a Homogenous Infrastructure Environment where budget is not a challenge. It is not at all suited for a Heterogenous Environment, e.g., a Public cloud where integration becomes a huge issue, also in SMB sections where budget is challenging.

Incentivized

• Performance and accuracy of cross-module dependencies.
• Simple to write and easy to understand.

Incentivized

• Building virtual racks
• Managing the customers' network and security
• Simplicity but the completeness of IaaS solution
• Integration with major software providers

Incentivized

• Cloud enabled Solution.
• Support Container based Apps.
• Cost efficient.
• Supports both Public and Private Environments.

Incentivized

• No dependency management tools (but there are no cross-platform tools of this type anyway)
• Tedious to do cross-compilation (Debug & Release builds, 32- and 64-bit builds, x86/ARM builds)

Incentivized

• The add-on/extension required on the internet browser sometimes are difficult to get working at first. We've experience instances where the add-on/extension latest versions will not work and have to downgrade to an older version.
• The server console lacks features and tools. For example it would be useful to have a copy and paste tool or a file upload tool.
• The vCloud Director management site uses Adobe Flash, which makes it impossible to use on a mobile device.

Incentivized

• The Deployment is complex.
• Recommended Number of Physical Nodes is three or more; with less than 3 Nodes, it becomes difficult to install V-SAN.
• Need for better integration. If we go on the public cloud, it is a huge challenge while integrate with an open source platform.
• Cost can be marginally reduced. SMB segments still prefer a separate license instead of VCF, or they postpone their purchase plans.

Incentivized

In general, it is fair to say the support is sufficient although we do not deal with support directly. There are a lot of forum people chiming in with suggestions or recommendations of particular usage or issues we run into. Since it is open software, patch and fixes will be available from time to time. A lot of information is available in the web now for knowing GNU Make from learning, example, teaching, etc.

Incentivized

I'm a full-stack developer that has used various build tools, including Maven, Gradle, and NPM/yarn. For our C projects, I also investigated CMake and Ninja, but they seemed more difficult to learn and more tedious to work with. GNU Make is a single binary that can be easily downloaded, even for Windows under MingW32, is straightforward to learn, and works pretty well despite its age.

Incentivized

vCloud Director is definitely my favorite as far as cloud managers. The only thing that compares is Cisco UCS Director, but it has slightly different functionality and purpose. I understand why a lot of clients still go with vCloud Director even though VMware intends to sunset it

Incentivized

Although the public Cloud Model follows Opex Costing Model, it actually leads to very high costs also, the infra model in my organization is not suited for a Public Cloud Model. Hence We decided on an On-Premise Model, and the best suited was VMware Cloud Foundation, which is a complete Software-Defined Scale-Out Architecture. I also prefer a Homogenous environment; i.e, support and services from a Single OEM, so that I Can get faster resolutions to my tickets raised.

Incentivized

• Streamline the build based on a lot of existing component being done, reusable.
• Commonly understandable, therefore, rampup effort is small.

Incentivized

• Saves a lot of time, and time is money
• Stable, so little to non downtime
• With P1 , good support

Incentivized

• My organization has a size of 1300+ employees, using multiple applications and an exchange mail server that is hosted on On-Premise Cloud, hence scalability has not been a challenge.
• Having hosted my Production environment and Mail exchange Server on VCF, there has been optimum resource utilization with very little scope downtime. Hence have been able to save a lot of funds on Hardware resources.
• Due to the size of my organization and due the data load, I have been able to save on Resource Utilization and Organization Funds

Incentivized