Kubernetes is an open-source container cluster manager.
N/A
Microsoft Dynamics 365
Score 8.0 out of 10
N/A
Microsoft Dynamics 365 is a CRM providing sales, marketing, and service functionality. It is offered as SaaS and on-premise. Dynamics 365 is part of the larger Dynamics suite of business intelligence and ERP products.
$44
per month
Red Hat OpenShift
Score 9.2 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
I used OpenShift v2 - which was pre-Kubernetes. (It now uses Kubernetes under the hood - but keeps it fairly hidden). Kubernetes was a ton more stable and easier to use. No more custom CLI to use in order to script together deployments. No more messy ‘push your entire code …
It stacks well against OpenShift. The only downside for OpenShift is the multiple operators and the custom logic implemented in the product, plus the upgrades, which tend to be a bit longer due to the more complex implementation. Overall, these are similar products but with a …
Kubernetes cluster is cable to manage multiple nodes on on-premises or cloud infrastructure. In Kubernetes, we can easily add new nodes when ever required. We can easily update and rollback our application hosted on Kubernetes with the help of rolling and blue green deployment. …
Verified User
Administrator
Chose Kubernetes
I didn't have too much experience or exposure to OpenShift but I do remember that in certain areas our organization found Kubernetes to be more useful and met our needs in comparison to OpenShift. Although I can't compare, I think it's easier to customize Kubernetes because of …
Comparing the 2, open source Kubernetes is quicker to setup by about 75%, less restrictive, and free of course, but it lacks the security and support of Red Hat, and deploying features is much harder compared to with operators. For buisiness purposes, OpenShift is just more …
We looked at a few other options like plain Kubernetes and some managed services, but Red Hat OpenShift stood out because it’s enterprise-ready out of the box. The built-in security, automation tools, and support made a big difference.
We explore a lot of services to use in. But in todays world everything is cloud and the on premise solutions are not very strong until we discover Red Hat OpenShift which still very committed to maintain on premise solutions, we select Openshift and since first day we are very …
Red Hat OpenShift was the product that my team has been using since I've joined so it has been the only product in this area that I have used. With that being said, I have really no complaints and love implemented Red Hat OpenShift in my work to help be more efficient with my …
greate UI UX, easy to use, even when you have no clue about any command lines, you still can manage your apps. Also, public documentation is great, if you search for anything you can find it online. A great community and a support system
Red Hat OpenShift has a better security posture than EKS. I enjoy the console on Red Hat OpenShift more as well. I believe there is greater observability for Red Hat OpenShift.
RedHat OpenShift can run on-prem and on Azure, meaning we can get support from RedHat from two platforms, despite it being on those different platforms.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Provides our company access to manage and customize the folds tailored to our needs. We needed to have certain paragraphs on certain paperwork per customer. MD 365 has those options to customize where needed and remove when not. The system is easy to navigate, and training can be done in a matter of days, even without prior knowledge of the system or similar systems.
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
Best to use for AP - like in our organization, there are plenty of AP bills, so with Dynamics, we can quickly enter the same into the Excel utility, which means CSV-based upload, and then we can easily upload the same to the software. It's a time saver.
Best for Bank reconciliation - MS Dynamics makes Bank reconciliation easy. Banks can easily sync with software and easily get reconciled.
Generating invoices to customers and directly sending them to their inbox is easy with this software.
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Small learning curve, obviously. You won't figure this out in a day, a week, or even a month. But given time, you can learn to be an expert. Or you can always get a consultant or hire in somebody. But learning the tool isn't out of the questions by any means.
Licensing can be confusing at times and isn't cheap, but it is cheaper than Salesforce. Plus no additional fees for data calls to better integrate your D365 CE data with other systems.
The Classic user interface left a bit to be desired, but now with the much-improved Unified Interface, the web client and the mobile client look the same, much more modern, and have more flexibility and power behind them for customizers as well.
I wouldn't necessarily say there is look everyday technology transform. I can see a trend wherein Red Hat OpenShift is adopting all the new technology trends and helping their customers align with their priorities and the emerging technology trends. I wouldn't call out various scope for development every day. There is scope for development. It is all how the organizations adopt it and how they deliver it to their customers. I don't want to call out there is scope for development. It's happening. It is a never ending process.
At the moment, I don't have anything to call out. We are experiencing Red Hat OpenShift and we can see every day they're coming up with new features as and when they come up with new features, we want to experience it more and more. We are looking for opportunities wherein this can be leveraged to help our users and partners.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
CRM has allowed us to keep all of our data in one place that is easy for all users within the company to view. I came into the company after they had been using CRM for about 4 years. They have all said that since we have used this it has helped us control work processes better, it has allowed us to be able to track things so much better, and has been something that has helped unite many processes that used to be all over the place. We are currently using CRM 4.0 and are planning on upgrading in the next 18 months to the 2011 version. Support for 4.0 is almost all but dried up. Understandably so. Some of the customization we have done, and a plugins we use, are now contained within the 2011 version so we are looking forward to that upgrade. We use an email marketing company as well, and they primarily support the 2011 version, but their product connects and is integrated within CRM. This is a great benefit as well so that all of our marketing information can be contained in one location.
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
The usability is easily adopted for users familiar with other Microsoft products. Dynamics 365 has several interfaces that cross over browsers and tablets. These multiple interfaces will be phased out and updated to a single unified interface eventually to provide the same usability across all devices. The backend configurations is slowly improving with the introduction of PowerApps compared to pre-D365 Online versions
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Our partner, Ledgeview Partners has been FANTASTIC to work with. They are always timely in their response and have taken time to understand our business and our specific needs. We've made a lot of advanced customizations and they have been a great help in making those updates.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
We used a data warehouse to house our data, and our IT team and implementation vendor worked diligently ahead of time to construct idea implementation plans. Out of millions of records- we had less than a dozen errors, which is remarkable. My major insight is simply having a group of completely devoted individuals working towards your goal who fully understand the desired outcome. Focused resources for implementation season are critical to success.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Microsoft Dynamics was part of a system overhaul for a local school, and we looked at many products. If we had used it for a company with low turnover, then it might have been more feasible. They needed something a new person could learn quickly, someone who might also be learning marketing terms at the same time - especially if there is nobody to train the individual now expected to know the system. Similar issues occurred with all of these programs (we called it being too big for their britches), and one of the bigger things we liked was that it is more compatible with MS Office products in both technical and visual appeal. If you have a steady employees who use a CRM consistently, low turnover, and those who are very familiar with Office products, Dynamics would be the smartest option for you. Unfortunately, this was just not true for the school environment
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
On our purchase, I'd been interrogated about our usage. Our needs are met by Microsoft Dynamics 365, which is simple to use. With so much data and information available, we must ensure that it is presented correctly to managers. Due to a lack of use, we don't have to spend as much money on Salesforce.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
My company's preferred program right now is Microsoft Dynamics 365. We use it to keep track of customers and important sales metrics in a streamlined manner. Anyone familiar with CRMs will find the tool extremely useful. Considering that we have a good turnover, this product will be used for its basic segments. As a result, there are few chances of error with Microsoft dynamics because it is so easy to use. Many options for recording data on these leads are available. It meets our needs and pays off.
For those without a centralized, all in one solution for major HR, Finance and other departments, Microsoft Dynamics 365 has vastly improved employee time utilization and profit.
Migrating clients from on-premise to the cloud has reaped benefits including better security, no unscheduled downtime and frequent updates to functionality.
Those transferring from cheaper solutions have lost money in the aim to be better integrated with other Microsoft products and AI they don't really utilize.
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.
