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
Workday Cloud Platform
Score 7.6 out of 10
N/A
Workday Cloud Platform is a PaaS designed to help developers extend the Workday platform.
N/A
Pricing
AWS Elastic Beanstalk
Workday Cloud Platform
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
No answers on this topic
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Workday Cloud Platform
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
Workday Cloud Platform
Features
AWS Elastic Beanstalk
Workday Cloud Platform
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
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.
Workday Cloud Platform is primarily suited for large organizations with individual teams handling various Human Resource functions. Since the data is scattered, Workday is an excellent tool to bring all the data to a single platform and then use Machine Learning techniques to generate both descriptive and prescriptive insights to make sure the skillset portfolio remains updated.
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.
The platform is quite intuitive to use, even a new user would find be comfortable navigating through different options.
As a lead, you can easily track the performance, leaves, and any recruitment in process.
The objective setting process and providing your inputs onto the same is pretty organized, easily accessible. Additionally, one can easily navigate through the historical objectives and performance feedback whenever one wants to review.
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.
Glitching - Occasionally the app will glitch and shut down completely. Sometimes it can be when you are in the middle of something timely, causing frustration and issues. I haven't seen this happen as often recently.
Inbox - It would be helpful if Workday developed a feature to organize inbox tasks based off what department they are for, what the task is and so on. So you can quickly filter or look for the task at hand.
Candidate Tracking - Hiring managers throughout the company work with the HR department to track candidates, schedule interviews and so on. Workday does not always have the best interface in this regard. It could use a feedback feature for hiring managers to be able to be more involved, as they can be on other platforms.
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.
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
Simple HR tasks are easy to complete (ex, hours, booking time off). It has a clean UI, but not sure we're using the full functionality as only certain tiles are shown.
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.
I give it this rating because, in its current capacity, it does not meet all of Human Resources' needs - which can cost the organization by having to rely on multiple platforms to do what one might be able to do. Again, as mentioned, it works great for what most employees require of it
- 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.
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.
Workday is an incomplete product, by this I mean it must work alongside other products and does not work by itself. Trying to make several different products work smoothly together becomes very challenging. As compared to ADP products, when purchased all together work very well all together. Also, ADP has extensive Training programs and extensive Customer Support. So ADP's products are far superior to Workday's products in my opinion.
