Just one person is enough for the deployment and maintenance of the solution. Any new updates are automatically pushed in if you configure it; that way, they are automatically pushed into your environment, and you will be notified that new updates are available, and you can easily install it.

The solution can be implemented by one person. We did the deployment.

The product can be deployed in-house by getting guidance from the Internet.

We used an in-house team.

The solution was deployed by the vendor.

In our web and desktop application development workflow, we typically support IT personnel by providing them with the necessary components to set up a server for deploying our applications. We hold weekly meetings to discuss our approach and progress, and throughout the week, we collaborate on various tasks. Once the work is completed, we publish the applications to the server, ensuring that all required roles are fulfilled for successful deployment.

For deployment, we didn't have to do much as it was already completed for us. Additionally, we utilized GitLab and Jira in conjunction with Docker for streamlined deployment processes.

The solution takes only a few minutes or hours to deploy.

Just one person is required for the solution's deployment.

We deploy this solution by ourselves. We never have had to reach out for help from vendors or other consultancies for the product itself. The programming is a different thing and is not the fault of the product.

I did the implementation myself. However, I would recommend using a team of experts for the deployment and maintenance of the solution.

Hitachi Consulting and Oracle Consulting have assisted us in other companies.

Started as part of a school program.

The shift in the deployment and maintenance is evident, as manual installations are no longer the norm. Intelligence is now directed towards automation, emphasizing the importance of testing. Once this process is completed, confidence in the system's functionality increases, alleviating concerns about manual loading and ensuring an automated and efficient workflow.

Everyone in our organization follows the mindset of having our proprietary tools. The majority of our internal tooling is developed in-house, making us predominantly a .NET-centric environment. While it's true that we also provide Java solutions, most of our confidence lies in .NET due to its reliability. Reflecting on past experiences, there were initial concerns about how autonomously and optimally .NET could run, especially in terms of memory management. However, over time, particularly with the introduction of .NET Core, those concerns have dissipated, and I am now completely confident in the reliability of .NET.

We implemented this solution using our in-house team.

I lead a development team and the team members perform the deployments. There is a lot of guidance available on the Microsoft website that is really good, so the deployments are not troublesome.

We have guys take care of the server section and we have our developers that implement from the installation for the environment.

It seems very easy for them to get everything up and running.

We used consultants for the deployment and we use third-party business intelligence tools for the integration.

Our company includes 40 skilled engineers who implement the solution for our customers. 

I handled the implementation myself with the assistance of my team.