Likelihood to Recommend Red Hat Decision Manager is well suited for developing a microservices-based application architecture where reusable components / APIs can be used across different end-user applications. It however may not be well suited for use cases where business users need low code / no-code environment to maintain business rules themselves without any developer / IT team support
Read full review If you are in the data science world, Scala is the best language to work with Spark, the defacto data science data store. I think that is really the main likely reason I would ever recommend Scala. Another reason is if you already have a team of programmers familiar with functional programming, e.g. they all have years of Haskell experience. In that case, I definitely think Scala is a superior and faster-growing language than Haskell and that picking up Scala after Haskell should be quick.
Read full review Pros Business rule management for filtering the candidate Automate the possible decision making which reduces the time and increase the productivity Whenever business rule changes based on the client requirement. Read full review Organizing different playlists. Coordinating content schedule and running time. Read full review Cons It should be easy to use because it needs more knowledge You should be trained to your partner well Well Documentations are needed Read full review The built-in compiler, scalac, is sssssssssslllllooooowwwwww. I mean like, if you thought the Java compiler was slow, try Scala! The default compiler on my 12k line codebase takes 4 minutes to compile from scratch on my i7 quad-core machine. This can be mitigated through the paid solution of Hydra which compiles your code in parallel. Unfortunately, it's quite expensive and your legal department or finance department may not approve of it. But if they do, for me, it reduced my compile time down to 80 seconds, much more manageable. Scala is not going anywhere and support for it is slowly dying. This is the main reason I would not choose Scala for my next company or project. Important Scala libraries such as secure social (which is used for OAuth, a major requirement of every web app) are hardly maintained. Another library that suffers from lack of updates is Slick, the database mapper. There aren't enough engineers working on it to even provide support for the new features that came out in Postgres 9.0 (e.g. JSONb). There is simply not enough of a community to drive Scala forward and keep 3rd party libraries up to date as Java world does it. As a corollary of a stagnant community, hiring Scala developers is hard as well. Of the 30 backend engineers we've hired, only 3 came in already knowing Scala. And as I will mention below, this is a BIG problem because learning Scala is really tough. The learning curve for Scala is very, very steep. Anecdotally, I came into my current company with strong Java experience. Java is the closest language to Scala but it took me 6 months before I stopped needing to pair program on easy tickets. It doesn't help that Scala has some weird syntax like Map[A, +B] and that it forces you to do functional programming. Read full review Likelihood to Renew Red Hat Decision Manager can be scaled and adapted to meet the automation needs of the organization as it grows by reusing the components and business rules data which provides a high ROI on the renewal costs.
Read full review Usability Implementation phase is very difficult .Of course ,you need to know bunch of things about cloud,container,automatization
Read full review Support Rating The support for Red Hat decision Manager can be improved to be more omnichannel with better response times for the customers.
Read full review The customer service team is very responsive and usually returns calls or emails within a couple of hours of placing a request or inquiry. Just about every rep I've spoken to has been very thorough and helpful, walking me through each problem and explaining the solutions in a way that's easy to understand.
Read full review Implementation Rating For high volume and / or complex set of legacy business rules, plan for adequate time for data migration activities.
Read full review Alternatives Considered If you have a low budget to invest probably JBoss BRMS is the option for you, if your budget is not restricted you'll probably like to consider Bizagi
Read full review Return on Investment Quickly write business rules Computers can take decision Complex event processing Read full review Negative: slow engineer onboarding. As I mentioned before, it took me 6 months to get up-to-speed on Scala and didn't need to bother more senior Scala engineers anymore for help with every ticket. That's hundreds of hours I wasted of myself and other engineer's time. Positive: thread safety, no concurrency bug. The ROI on this one is really hard to calculate, but I do believe Scala has saved me hundreds of hours over the past few years by allowing me to never have to worry about deadlocks or race conditions. Scala is simply so safe we've never had race conditions within the JVM before. Negative: third-party libraries aren't maintained so we have to fork and update them ourselves. As I mentioned before, we use Securesocial but it stopped receiving updates and there is simply no alternative to it. So, we forked it and put an engineer on it for a month to get it back up-to-date. What a waste of his time! Read full review ScreenShots