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

Alfabet Enterprise Architecture Management 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

Alfabet Enterprise Architec...
Ranking in Enterprise Architecture Management
17th
Average Rating
7.6
Reviews Sentiment
5.3
Number of Reviews
3
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 Alfabet Enterprise Architecture Management is 2.2%, down from 2.6% 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%
Alfabet Enterprise Architecture Management2.2%
Other97.4%
Enterprise Architecture Management
 

Featured Reviews

AlanJackson - PeerSpot reviewer
Partner: Enterprise Strategy & Advisory at a tech vendor with 10,001+ employees
Great taxonomy support but raw business processing should be upgraded
Alfabet is not just a technology tool, it's also a business tool. And if a decision's made without the business involved, then Alfabet will not be in a position to deliver anything more than support for enterprise architect drawings and solutions drawings. It has to be the business. If you do that, it works well. If you don't and I've had the experience where they haven't evolved a business, then it just becomes a tech tool that the business doesn't care about. The stigma of having an environment that was so delayed in the maintenance caused lots of finger-pointing within the organization of who was right and who was wrong. It took a considerable period of time to move people past that point to actually look at it as a business tool supported by the technology team. I rate the solution seven out of 10.
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 most valuable features are the completeness, and the repos included on the platform."
"The most valuable features of this solution are its customizability, and flexibility in the configuration."
"The initial setup was straightforward. It takes two to three days to set up the environment. One person was able to handle the implementation."
"For us, adopting this solution was the right decision."
"The taxonomy support across all the phases is the most advantageous feature."
"Serverless has positively impacted my organization as it has become the de facto standard for any POCs I have been doing, unless something specific is required that demands an on-demand instance."
"In terms of time or cost saved compared to before using Serverless, I save approximately 60 percent of my development time because everything is very lightweight and gives me the freedom to work within Serverless."
"Serverless has positively impacted my organization because the outcome was very positive in most of the projects we used it, especially with the fast delivery made possible by clear boundaries for each function and the ability to resize the team constantly without needing to think too much about that, while the price remains very reasonable."
"Serverless offers many best features; it is really easy to use, very developer-friendly, and has a great community."
"Serverless has positively impacted my organization by shifting our focus from infrastructure management to pure product delivery."
"Serverless has positively impacted my organization by making us more agile in giving releases, which has benefited my teams by allowing us to continuously maintain our Node packages and different scripts, which are now more easily manageable."
"Making use of Serverless has at least helped us save 50% in cost spending on resources."
"Serverless has positively impacted my organization as it has been a good experience for the team overall because it is a new framework that we had to learn, and cost-wise, it helps because moving to Serverless means you do not have resources spinning all the time."
 

Cons

"The product is not great at implementing security frameworks across an end-to-end supply chain."
"The user experience, the layout and the different technologies behind the presentations are a bit old. These need to be updated. They should focus on web development. It's simply not supporting the current user experience guidelines."
"IT governance in this solution needs improvement. We would like to see the visualization of assets, as well as artificial intelligence techniques to assist us in making our decisions."
"Serverless is not suited for production environments."
"We have been using this framework for a long time but now feel the cost is expensive, so we need to improve in this area."
"The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless."
"Sometimes we see old results instead of new results when events trigger."
"I see that the local development setup in Serverless is more complex, so if you provide examples or automation that we can test and deploy locally on a local machine, then automatically shifting all methods or functions into production would significantly improve efficiency."
"Serverless can be improved with more usage videos."
"I choose eight out of ten because to go ahead with Serverless, we need to do YAML file creation and other format file creation."
"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
18%
Manufacturing Company
14%
Energy/Utilities Company
7%
Outsourcing 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...
 

Overview

 

Sample Customers

Metro Bank, Credit Suisse
Information Not Available
Find out what your peers are saying about Alfabet Enterprise Architecture Management vs. Serverless and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.