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
SAP Business Technology Platform
Score 8.5 out of 10
N/A
SAP Business Technology Platform (SAP BTP) is the company's Platform-as-a-Service (PaaS) offering, that brings together intelligent enterprise applications with database and data management, analytics, integration and extension capabilities into one platform for both cloud and hybrid environments, including hundreds of pre-built integrations for SAP and third-party applications.
N/A
Pricing
AWS Elastic Beanstalk
SAP Business Technology Platform
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
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.
SAP Business Technology Platform is highly suitable for AI agentic development, particularly when workflows require dynamic orchestration, modular service integration, and real-time decisioning. However, it may be less effective in environments where backend services are fully encapsulated and do not expose interfaces or events that SAP Business Technology Platform can interact with—limiting its ability to orchestrate or extend those services meaningfully.
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.
Services are operated by SAP with outstanding support, always giving a helping hand even if it is custom code or solution provided on the platform
Services are easily connectable via standard approach to our backend SAP systems in SAP Rise/HEC
Secure access using identities from our existing identity management helping us to safeguard data security from within SAP systems up to custom frontend applications
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.
For IAG, if there are multiple roles it can be overwhelming from an UX standpoint.
Controlling and identifying shadow user creation is not as intuitive.
Unlocking admin rights to an environment seems very easy if having elevated permissions, this seems like something that should have more controls rather than being able to unlock admin rights yourself.
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.
Seamless integration with external system and dashboard to monitor the data flow and analysis are very essential for the business. The way the product is designed and modelled lead to minimum business disruptions. Adopting to the new and modern technology was easy. Keeping the central system as clean and adopting project bases development are advantages.
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
Okay, so the content that we have built on the platform is limited to specific testing on the iFlows within integration suite. The visualization layer is nice to use and helps with the design elements, however with developers that are more used to markup languages, it doesn't have the same CLI type feel when you want it. Perhaps the majority of users are that deep, but other platforms have a better CLI type developer experience.
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.
The biggest problem we ran into was communication between SAP Business Technology Platform and onsite resources. Unfortunately our SAP Business Technology Platform and Cloud systems are under different customer numbers. I constantly had to open tickets under each customer number because I was unsure of where the issue lied. And having to create a dummy ticket for our ECC systems to open the ECC connections for another ticket under the Cloud customer is a pain.
Training material in Developers Community or from Learning hub are really good... also most of the time we route through Discovery center... so materials provided by SAP is really good.
- 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.
Having a full cloud native environment for devlopment of microservices and digitals solutions while having standardized access to our core data on SAP via cloud connector is one of the main benefits of using BTP over others hypervisors. BTP is the standard hyperscaler as soon as something relies on data from SAP systems in our company now
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.
Initially, SAP Business Technology Platform works hand in hand with S/4 HANA and the SAP product suite, but also can go and extra mile and integrate with other non-SAP products and services at hand. It's capable enough to understand the ERP use cases component and develop intelligent applications to satisfy the users.
Still using traditional devops instead of using build. Very high cost in development.
Still using Node.js instead of REST ABAP. Additional cost of resources. Migration of current CAP to RAP will be costly and do not have a business case yet. Continue with multi-language is costly.
Integration suite is power but the migration from PIPO to IS has been more challenging than being advertised.
