Apple iCloud is a document management software offering from Apple. It includes features such as access to music, photos, calendars, contacts, and documents, and it is built into every new iOS device.
$0.99
per month
AWS Elastic Beanstalk
Score 8.4 out of 10
N/A
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).
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
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
Pricing
Apple iCloud
AWS Elastic Beanstalk
Google App Engine
Editions & Modules
50GB
$0.99
per month
200GB
$2.99
per month
2TB
$9.99
per month
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
The biggest thing is Apple doesn't lose versions and changes. With Office 365 and various Google corporate programs, they would track versions — but not well. If someone sat with a file open and later closed it after a colleague had made changes, some of those changes would get …
Competitively priced, sometimes less expensive depending on storage needs. Apple iCloud is much easier to use on a macintosh computer since it is built into the operating system.
As I have mentioned, the seamless integration across Apple's ecosystem is what keeps us using this product. However, the robust value of the Microsoft 365 Business Premium suite and functionality of their AI companion - Copilot - makes it superior at an organization level. The …
For me Apple iCloud is the superior choice. Google Drive is acceptable but it feels much less safe (to me). I disliked MS Azure and would never use that system.
Apple iCloud allows to track devices when lost and uses end-to-end encryption for data such as iMessages of Health data. It also includes features of shared albums to optimize storage and can access these items through any Apple device in a quick and efficient way.
Egnyte was a good system, but there were two things that I didn't like. One, once your data was in their server, it was in their server. It came across as you did not have control or even ownership of it anymore - plus you had to maintain the payments to them, or it was all …
Dropbox is more universal but has a higher price point that Apple iCloud and google while mid price point offers more options in software that allows for file editing and sharing directly in the document. Apple iCloud does not have that on offer. Apple iCloud is the lowest …
Nowadays local storage are having a lot of bottleneck and upgrading process require time and money, iCloud are one of the safest and most secure platforms, its End User License Policy is in favor of customer and reliability. Apple iCloud collaboratively works with iOS and macOS …
Google Drive is similar to Apple iCloud, but since I prefer Apple products and have operated within the Apple ecosystem for many years, I use iCloud. Some clients who don't use Apple share documents with me in Google Drive so I have experience with the product, but I prefer …
Dropbox is the king of cloud environments, and where Apple iCloud should go to. I have tried others but don't even remember their names now. We have our own personal cloud as well. I have used cloud environments since 2007 and would love to see Apple iCloud step up to a full …
While I have to use Dropbox on occasion, I greatly prefer to use iCloud for file sharing. I also have used Google's Apps, and because I'm a Mac/iPhone user, iCloud has more easily fit into the normal routine of what I'm already doing and using. Dropbox has some minor features …
Apple iCloud is specially made for iOS devices. Nothing and no one will ever be able to service an Apple product's needs better than Apple themselves. The Apple iCloud software is designed specifically for iOS devices, ease of use, and mindless security for automatic backups. …
The basic premise among these is the same. Where Apple iCloud stands apart for our team is that there is not a separate app to be downloaded to access these features on most phones or tablets (most of our staff has iPhones, and we provide iPads). This allows everyone to obtain …
The security and functionality of iCloud beats out any other products I've tried. While two-factor authentication is available elsewhere, Apple seems to take security a step further with notifications across all devices. In addition, the pricing is right - the low cost of 1TB …
We have found that Google Backup & Sync and Apple iCloud between them have all the bases covered. While Google is excellent for many things, as an Apple-centric environment, we utilize both systems. Between them, we have been able to reduce our expensive on-prem file storage …
Overall, iCloud performs quite well against some of its larger competitors. In my opinion, iCloud may be better suited for personal and social sharing compared to business cloud platforms like OneDrive and Google Drive. iCloud is incredibly strong if your organization is fully …
Amazon AWS interface is clunky and too unintuitive for me. It's like going from a Mac to a Windows machine. YUCK. I realize that Apple iCloud is really just relying on Amazon AWS servers for data storage but it's so much nicer to work with the Apple interface for my daily data …
They are different platforms but both reliable and easily used by those who need to access and use it. I am a happy customer for both Apple iCloud and Boomr and would highly recommend them to anyone who is looking to use and purchase something to give them the reassurance and …
One Drive can allow users to collaborate in realtime and rare crashes on documents. The storage is very generous, and pricing for business, especially non-profits, is fair. One Drive also allows for better photo storage for us as a school. We can keep yearbook items and also …
Already a part of the Apple ecosystem, so if it suits our needs, we will use it. We have a Department shared Dropbox account specifically for sharing large projects with vendors, so Apple iCloud is for lighter internal projects such as shared spreadsheets for project …
Apple iCloud is extremely similar to Google Drive. You’re able to access files from anywhere, even a PC, without needing to be on the device where the file was originally created.
iCloud is probably the best option for someone who uses primarily Apple devices and services. If you are multi-platform in your technology use I would make sure you test out the free version of iCloud before you make the switch, Apple likes to play nice with Apple, which means …
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 …
As it supports end to end flow of application deployment and not a part of any individual process like other AWS products, AWS Elastic Beanstalk can be a game changer in cloud industry.
The AWS platform provides a great deal of configurability that is abstracted and provided very well through AWS Elastic Beanstalk. This is the main reason for choosing Elastic Beanstalk over competing services. Another reason for selecting AWS Beanstalk was vendor …
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 …
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.
Public & Private Cloud Senior Business Technology Engineer
Chose AWS Elastic Beanstalk
We now default to Amazon ECS, due to flexibility this gives us with how workloads scale, and more network flexibility as many of our workloads are internal / external facing. We selected Elastic Beanstalk at beginning of our containerization phase, which suited our needs …
Azure currently doesn't have a solution that's similar to this but you can do a lot of the features with several of the components that Microsoft Azure offers. AWS Elastic Beanstalk exists in that niche market where if you have an existing solution, this is a great way to move &…
AWS is much more focused on scalability, but Heroku was much easier to get things up and running as a beginner. For simple hosting, I would stick to something like Heroku or Netlify. That said, Elastic Beanstalk is meant for more performant functions requiring large scaling and …
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 …
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 …
I enjoyed that Lightsail was so simple to provision and access via the in-browser SSH terminal, but ultimately Elastic Beanstalk is a more robust offering that interfaces seamlessly with more of AWS's other services. Elastic Beanstalk is also better equipped to automate …
I selected these solutions because they are the closest to being able to set up separate server or VM instances. As far as performance and scalability, Heroku does offer an autoscale option, but the base cost to have the autoscale in place, sets Heroku behind EBS. Digital …
Honestly, I haven't tried any other alternative products. As already mentioned, I am already heavily invested in AWS, so EBS was a natural choice for me. In other reviews, I have found, AWS is better than its competitors. There are more flavors, and options in AWS, better …
Heroku is another similar product which we had tried out to deploy one of the NodeJs project and it has lot of developer friendly features as well. Though Heroku is more expensive than Beanstalk is what I found. Heroku also has some restrictions which can affect the …
The other main competitor that I have used would probably be Heroku. While Heroku is incredibly simple and easy to get a sample web app online, its dashboard and product connectivity didn't feel quite as seamless as AWS Elastic Beanstalk. AWS Elastic Beanstalk has a higher up …
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 …
For our organization, we selected Google App Engine which provides a reliable and efficient way to create and deploy apps moreover it supports a lot of languages and provides automatic debugging of code which enables us to deploy code to production as soon as development is …
If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
It's the manageability of the Google App Engine which made it a better option in our case. It's quite straightforward to deploy on App-Engine. No worries for monitoring setup
You can create and scale Kubernetes clusters quickly, but you have to keep an eye on that cluster. In-App Engine, you don't have to worry about infrastructure, but in some scenarios, Kubernetes fits better.
Google App Engine is the first product we picked up to store the mass data. Later we came to know that, firebase database is also similar to Google App Engine. But still, we didn't step into it. We will try it later.
Azure App Service is in par with Google App Engine although you may want to use Azure App Service if you are integrating with other Microsoft IT components, for example SQL Server. Google App Engine is great when in long run, you will be using Google cloud components, for …
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if …
Google App Engine is very easy to use and mostly up to date makes it compatible with all old and new devices. The applications are very interactive and the prices are accessible for most users. The prices tend to get slightly expensive as we head on towards higher …
The two giants are Google and Amazon. Both are very similar however Google App Engine allows you to deploy your web applications through platforms like Python where as if you're using AWS, you have full control on the operating system services. Google is good because you pay as …
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 …
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 …
Google Apps is great for environments where the need for a more robust platform is not necessary if you are looking to have email and cloud collaboration enablement of your working staff. From the stand point of using both, I can see the value of both but it really depends on …
AWS and Heroku are both great, and I use them both extensively for different projects. Google App Engine was chosen because it is much more innovative than AWS, and because Heroku specializes in Ruby on Rails. Even though Heroku supports Java and other services, we feel Google …
With GAE it's a matter of "code your app and deploy it". You don't care on what servers or on how many servers it runs. System administration is done for you. With AWS you still have to be a system administrator with good knowledge and undestanding of load balancers, database …
You can spawn up your own cluster using Kubernetes or Container Engine which will scale automatically when configured properly, but you have to keep an eye on that cluster. In App Engine you don't have to worry about it at all, just ship your code and it will run.
We chose Google App Engine because it supplies the most infrastructure per dollar spent. It's much more expensive to use Amazon EC2 to scale to over a million users. Also, the engine's narrow language support system, while somewhat limiting, makes getting started quickly much …
We left Lotus Notes for the (more versatile) Google Apps. We could never recommend the closed architecture of Lotus Notes. We have evaluated Office 365 and believe the product is compelling. So compelling, that we may consider a platform change…
iCloud is also great to keep access to photos synced across devices. Ex: I can snap a photo at a job site and have access to that photo on my desktop when I return to my office. I can then drop the photo into a document that is stored in iCloud and have instant access to that document on my iPad at a client's office later in the day. Seamless transitions make life much easier.
AWS Elastic Beanstalk is well suited for [the] rapid development of applications that use standard compute platforms based on popular programming languages. So getting a Go, Python, Ruby, or Node.js app going in AWS Elastic Beanstalk will be easy. For non-standard applications, containers provide another option for using AWS Elastic Beanstalk. In either case, AWS Elastic Beanstalk is well suited for applications that are [self-contained]. AWS Elastic Beanstalk is also good for development or test environments that need a built-in deployment method. AWS Elastic Beanstalk is less appropriate for complex applications that rely on multiple AWS services. While deploying and running the base code might be easy to get going, it may be difficult to apply permissions and integrations with the other services.
Google App Engine is especially well suited for situations where there is a variable workload during the day, e.g. inbound task processing with task queues. In this situation queues can be setup with parameters governing the process speed/scaling which allows you to easily balance performance with cost and meet a good balance.
Syncing files, appointments, Notes and contacts. If I'm away from home, and set an appointment using my phone, that appointment automatically updates real time to my home laptop and vice-versa.
Building an application that uses Google's Authentication, means users no longer need to remember an different user id and password. Once they are logged into to Google, they can seamlessly access your application hosted on Google App Engine.
Google App Engine automatically scales up and down. SO if your application receives a spike in user traffic, App Engine automatically launches additional instances of your application to cater for the increased traffic. Once App Engine detects that the spike is usage is over, it automatically scales down to handle the current traffic.
Google App Engine can be easily integrated with Google Cloud SQL, Google Compute Engine, Google Cloud Storage etc, so that you can build out a full application using one or more of Google's Cloud Platform products.
Customization - iCloud is great at the stuff it does well. But it lacks features that some competitors (in Google Drive or Dropbox) do really well. API support for third-party apps is really great for some other people.
Remote use - Managing or accessing information from iCloud while not on one of your logged-in apple devices can sometimes be an issue. From a work computer for example. It doable, but the experience is much less user-friendly.
Ability to edit documents on the cloud similar to google docs or some other competitors
How to more easily integrate with other other AWS services. There are plenty out there, but it's not quite as seamless as I feel like it should be to mix and match products.
Make backing up easier when scaling the server. It took quite a bit of time to make sure we had everything set up in case something went wrong.
When you are first starting to use AWS, the dashboard can be very intimidating. There are countless products all with names that aren't very indicative of what they actually do.
It's so seamless that I can't imagine another product doing a better job synchronizing all of my devices. I simply do not think about it at all. Everything happens behind the scenes and I'm confident that Apple keeps my data safe and secure. I'm a happy customer as far as this is concerned. I have not had a bad experience with this service.
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.
While it may be great to use with other Apple products, I find it's an absolutist-style workflow to be debilitating and to lead to many problems. When you sign into the cloud, it completely takes over your device in many ways that you don't notice at first until there is a problem.
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
Occasionally, large files that haven't yet been synced require a few minutes to pull down but I've rarely noticed delays. It does a good job of keeping data cached on my local machines while updating them with changes from other machines transparently.
I never used Apple iCloud support, but have never needed to do so. It has become more of a personal issue with computers in my organization, where the business solution has been with Dropbox. I do have to admit when my Mac went down, having things on Apple iCloud did help to get things restored. However, since I had more than one photo file for my Business and Personal data, I was not able to recover my Business Photos. Apple iCloud should have been able to do this.
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.
- 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.
As I have mentioned, the seamless integration across Apple's ecosystem is what keeps us using this product. However, the robust value of the Microsoft 365 Business Premium suite and functionality of their AI companion - Copilot - makes it superior at an organization level. The same could be said for Google AI (Gemini) as well as their cloud services like Drive.
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 platforms. The only thing is their documentation and UX are a bit old, which doesn't stop it from performing greatly, but yes, if you are looking for better UX, then you can check out other options.
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if that's what you need. It can tend to cost more as well. App Engine is far more straightforward but there are limitations if you need to change the environment. But even then, Google Compute Engine also compares to EC2 and stays within GCP.
Elastic Beanstalk removes countless hours from development team responsibility, freeing up those resources to instead focus on building the products that our customers want to use.
As a business that is already embedded into using EC2 instances, it's essentially free to leverage the work that AWS performs on configuring the Elastic Beanstalk stacks.
With Elastic Beanstalk, while there is still a responsibility to ensure that applications can work with updated underlying dependencies, it's much easier when AWS handled the heavy lifting of updating the stacks.