No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Rational System Architect vs Serverless comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Rational System Architect
Ranking in Enterprise Architecture Management
15th
Average Rating
7.4
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Serverless
Ranking in Enterprise Architecture Management
7th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
24
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Enterprise Architecture Management category, the mindshare of IBM Rational System Architect is 3.0%, up from 1.8% compared to the previous year. The mindshare of Serverless is 0.4%. It is calculated based on PeerSpot user engagement data.
Enterprise Architecture Management Mindshare Distribution
ProductMindshare (%)
Serverless0.4%
IBM Rational System Architect3.0%
Other96.6%
Enterprise Architecture Management
 

Featured Reviews

GM
IT/Business Architect at a financial services firm with 51-200 employees
Lots of valuable features, especially the metamodel customization
In terms of what could be improved, we did not take the whole package with all the modules, and I think that the integration with other platforms like Office could be better. The reverse engineering of the database is already there, but in the next release I would like to see some pilot supplied with the solution in order to address any database.
SA
Lead Software Engineer
Serverless workflows have boosted rapid AWS development but still need better CI and automation
Serverless has many advantages, and it is very easy to handle with a cloud solution. However, there are a few concerns about the limitations. Especially when I work with Lambdas, there are maximum Lambda timeouts. Likewise, there are several things from Serverless, such as maximum file uploads. Serverless can be improved by addressing the challenges faced when we have the first infrastructure. Sometimes it is hard because we need to manually create things such as Cognito pools. While 90 percent of the time is automated, more automation would be better. If Serverless provided CI/CD capabilities, that would also be great, as currently it only allows for manual deployments. Additionally, when working with cloud services, Serverless allows the use of LocalStack or Serverless Dev, but I think Serverless Dev might need simplification for easy access without organization registration. When considering needed improvements, I get frustrated with Lambda time and similar issues, which are actually not related to Serverless but rather are AWS issues. However, when discussing Serverless, the main points I see require improvement from the Serverless end.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The user interface is good. It's both clear and comprehensible. It's easy to work with."
"The solution is pretty stable."
"There are a lot of features I find valuable, but I think that the metamodel customization is one of the best features that the solution offers."
"We have seen ROI with this solution over the years that we have used it."
"The System Architect Product has greatly assisted the corporate strategic planning process in two areas: the simulation of scenarios for Enterprise Transformation Projects and providing a global view of Enterprise Capabilities and Functional Gaps."
"The main advantage of the solution and its most valuable aspect is the customization of the meta-model."
"My advice to others looking into using Serverless is that you can use it if you want to save money, if you don't want to manage servers, if you only want to be charged for the amount of time you use, and if you want to run code and ad hoc tasks."
"Serverless positively impacts my organization by being really cost-effective and serving as a production performance testing tool, as we increase the load, it automatically increases the CPUs and RAM without needing any manual intervention or heavy servers for this type of testing."
"Serverless impacts my organization positively in many ways by enabling us to easily debug issues when any pipelines break; we can get errors, debug them, and address issues."
"Serverless offers a great pay-as-you-go model that is really excellent."
"I can share specific metrics indicating Serverless's positive impact: I achieved 100% uptime, an impressive feat compared to traditional servers that often experience downtime during peak usage."
"Serverless has saved me a lot of money and time in my organization."
"The best feature of Serverless is cost; when the application is in use, then it will incur cost, unlike traditional servers where it is the cost of all the uptime."
"There is a huge impact as my traffic gets auto-adjusted, I do not have to worry about whether my server is capable of handling the traffic or not, Serverless servers are much more capable, and I just need to pay for whatever I am using."
 

Cons

"There needs to be more information at the outset about how to use the solution and how to deploy it. The deployment process needs improvement."
"The reverse engineering of the database is already there, but in the next release I would like to see some pilot supplied with the solution in order to address any database."
"Some aspects of the user interface lack a common navigational or functional framework."
"Integration with all other software, like Microsoft, to facilitate an exchange, is not great."
"The solution needs to better integrate with other products, like Microsoft."
"We are not happy with this product and are not planning to continue with it."
"It was sold separately and it is not very easy for somebody who wants to use the solution for modeling to think that you have to select specific modules in order to use the product."
"This solution can be more user-friendly and easier to use, with better dashboards."
"The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless."
"I would say in the debugging, we could maybe improve or in monitoring."
"Serverless is a very comprehensive platform. I have not explored everything, but I use it only for traffic management and the auto-scaling features. That is why I deducted one point."
"The biggest area for improvement in Serverless is around cold start latency, especially for applications that aren't constantly active."
"Serverless can be improved with more usage videos."
"I believe Serverless can be improved as I have faced some pain points and challenges."
"Serverless can be improved by effectively handling large scale applications, as large scale applications would save more money."
"With the upcoming technology change and the migration towards Generative AI and the exploration of large language models, it would be quite helpful if serverless services evolve with that."
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Comms Service Provider
10%
Manufacturing Company
9%
Healthcare Company
7%
Construction Company
31%
Financial Services Firm
11%
Manufacturing Company
8%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise5
Large Enterprise5
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Serverless?
Regarding pricing, setup cost, and licensing experience, I find the application to be very cost-effective. The headcount needed is much lower compared to supporting services in software development...
What needs improvement with Serverless?
Debugging distributed Serverless applications can still be frustrating. When multiple functions, teams, and events are involved, tracing a failure is not always straightforward. Cold start latency ...
What is your primary use case for Serverless?
Our main use case for Serverless is deploying APIs and background processing jobs without having to manage servers. We had several workloads triggered by API requests, S3 uploads, and scheduled eve...
 

Also Known As

Rational System Architect
No data available
 

Overview

 

Sample Customers

Wuxi Lake Cloud, Nationwide, ETI, IDS Scheer
Information Not Available
Find out what your peers are saying about IBM Rational System Architect vs. Serverless and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.