AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Google App Engine
Score 8.2 out of 10
N/A
Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
SAP Analytics Cloud
Score 8.2 out of 10
N/A
The SAP Analytics Cloud solution brings together analytics and planning with integration to SAP applications and access to heterogenous data sources. As the analytics and planning solution within SAP Business Technology Platform, SAP Analytics Cloud supports trusted insights and integrated planning processes enterprise-wide to help make decisions without doubt.
$36
per month per user
Pricing
AWS Elastic Beanstalk
Google App Engine
SAP Analytics Cloud
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
SAP Analytics Cloud for Business Intelligence
$36.00
per month per user
SAP Analytics Cloud for Planning
Price upon request
per month per user
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Google App Engine
SAP Analytics Cloud
Free Trial
No
No
Yes
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
A 30-day trial with SAP Analytics Cloud is available, supporting analytics enterprise-wide. A trial can be extended up to 90 days on request.
AWS Elastic Beanstalk is equivalent to Google App Engine in terms of product. I selected AWS Elastic Beanstalk because it was within the stack we were using, and it made sense for us given the other architecture.
I selected AWS Elastic Beanstalk mainly because we have been using AWS services for our company. Using AWS Elastic Beanstalk is relatively easier than starting to use a completely new cloud platform. But we are also reviewing Google App Engine, and found out Elastic Beanstalk …
In some of the other companies that I've worked in, I've had the opportunity to work with the above softwares where the structure and architecture of the services was much complicated but the above softwares were able to handle it with more ease and efficiency. The complex …
There are many services like AWS Elastic beanstalk, but there are none with the maturity in the platform or the cost-effectiveness of AWS Elastic Beanstalk. Also, AWS Elastic Beanstalk is the oldest among them, so there are more people with AWS experience than the other …
I have used App Engine on Google Cloud Platform and App Service on Microsoft Azure. Both offer similar capabilities to AWS Elastic Beanstalk. App Engine has the nice ability to scale to 0 instances when the application has not been in use for some time. This allows for …
AWS Elastic Beanstalk is a great option for an organization that's already invested in the AWS ecosystem. The greater the number of complementary features needed by the application (e.g. integrating with Amazon's Elastic Load Balancer, databases, etc), the greater the reward …
simpler and cheaper sums up the benefits. AWS became too bureaucratic while Google App Engine made he process easier to setup. Again, I just spent a few minutes to setup a simple app, setup a budget, add my credit card and have it up and running. Google is captivating its user …
We commonly decide between App Service, Elastic Beanstalk, and App Engine. Normally, we do not have a strong preference for the services, it really comes down to whether or not there are other factors drawing us toward a particular platform. In the case of App Engine, it is a …
I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -
I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
Scalability & Security comes with the service, which makes it the absolute perfect product for your business.
Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
>> Using SAC predictive analytics capabilities for inventory management in a Production line setup has helped generate Purchase Requisitions and Purchase Orders for raw or semi-finished goods without much head-banging into Demand management rules. It does it beautifully with seamless integration with HANA core MM and PP modules, along with BI integration. It has resulted in 30% greater warehouse storage capacity, thereby saving revenue from piled-up inventory and associated manpower costs. >> SAC sometimes shows latency in working out a large data set, thus giving a poor user experience compared to its competition. Also, it may occasionally show misinterpretations when embedding data from 3rd-party systems into the HANA core dataset.
Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
Common application architectures can be referenced as patterns during project [setup].
Multiple environments can be deployed for an application giving more flexibility for experimentation.
It makes it easier yo analyse order and related records easily.
We can easily maintain and track the performance of employees in organisation.
Can easily track various aspects for the growth of an organisation thus allowing real time analysis and tracking of organisation's growth and performance.
Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
SAC supports various data sources, but improvements in the ease of connecting to and integrating with certain data repositories, especially non-SAP databases, would enhance the platform's versatility and integration capabilities.
An offline mode for SAC could be valuable for users who need to access and analyze data without an internet connection. Additionally, optimizing performance for large datasets and complex visualizations would contribute to a smoother user experience.
As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
We are planning to review the licensing as we have issues with SAC dealing with huge datasets. Analytics area is good for import models but when we have live connections in place that's when we have issue with SAC dealing with huge datasets in live be it BW or be it HANA models in the backend.
The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
On a scale of 1 to 10, I would rate 8 SAP Analytics Cloud's overall usability as a 7. SAC has a clean, modern user interface with drag-and-drop features. It is an integrated platform that combines reporting, planning, and predictive analytics in one tool. It has Real-time connectivity with SAP data sources like S/4HANA.
Self-service analytics capabilities allow non-technical users to build simple dashboards.
I would rate SAP Analytics Cloud an 8 out of 10 for scalability. It offers a flexible, cloud-based architecture that supports expansion across departments and geographies. The platform adapts well to growing data volumes and user needs, making it a strong choice for organizations looking to scale analytics capabilities efficiently.
I would rate SAP Analytics Cloud’s performance an 8 out of 10. Pages generally load quickly, and reports run within a reasonable time frame, even with complex datasets. Integration with other systems is smooth and doesn’t noticeably affect performance. Overall, it’s a responsive and efficient tool for business analytics. But
As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
Since the implementation stage, the support team has been very helpful and assisting. Even in the later stages, the tech team had quite a rapid response. In general, SAP has provided us with great customer support, let it be for a specific product of SAP or for integration of different modules.
In hindsight, it would have been easier to have someone there in person. Questions were answered, but with 11 participants, it got a bit chaotic online
- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.
SAC is a simple solution ad it works fine when connecting it to other SAP tools. On the other hand, connecting it to third party solutions brings difficulties when there's no previous design and the objetives are not clear. It is really important to integrate Business users from the start to provide with valuable business insights
We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
SAP Analytics Cloud and Power BI are both tools that help businesses understand their data, but they have some differences. SAC, made by SAP, works well if your company already uses other SAP products. It's in the cloud, easy to use, and has features for analyzing data, getting insights, and planning for the future. Power BI, made by Microsoft, can be used in the cloud or on your own computers. It fits well with Microsoft tools, is easy to use, and can do advanced data analysis. SAC has built-in planning tools, while Power BI needs extra tools for detailed planning
Is good for use across multiple locations. It allows users to access data and reports from anywhere, regardless of their location. Can consolidate data from various sources, including different SAP systems and external sources, which facilitates cross-location analysis. SAC enables access to data and models from SAP Datasphere to create new stories. Detailed permissions can be defined for cross-departmental use.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
Many manual data manipulations and exports in Excel have been replaced by the tool, providing management with improved insight into the amount of time spent at each stage of an invoice's lifetime, allowing bottlenecks to be discovered.
We now have more insight into the data, and people with little technical experience can easily build stories.
