Azure Cloud Services is a cloud platform that enables users to create infinitely-scalable cloud applications and APIs. It enables users to build the web and cloud applications needed while also simplifying the management of applications with cloud services, and while ensuring high availability. Users can: scale an environment automatically based on demand and reduce costs, automate operating system and application updates to increase security, and take advantage of integrated health monitoring…
The Salesforce Platform is designed for building and deploying scalable cloud applications with managed hardware provisioning and app stacks. Lightning Web Components are used by developers to build reusable UI components.
$25
Per User Per Month
Upsun
Score 9.9 out of 10
N/A
Platform.sh helps companies of all sizes, from SaaS entrepreneurs looking to build, run, and scale their websites and web applications.
Microsoft Azure Cloud services is a good choice for hosting web applications, based on requirements it can be simple websites or complex web services as well as it provides automating application development and deployment pipeline. It's less appropriate in case of cost-effective option for organizations with tight budget constraints. For very basic static websites, Microsoft Azure's offerings might be seen as overkill.
If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.
In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.
Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.
As a certificate developer and consultant, I love using Azure, it's interface is developer friendly with well guidance and support. Also there are a lot of service for any work, Azure ecosystem is sufficient to complete your all developments needs. So based on that I feel Azure is good and gives better developer experience.
It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.
I am not an administrator so there may very well be outstanding Support and I am just not privy to it. On a user level it's hard to gauge the effectiveness and responsiveness of Support because nearly everything has to go through an administrator
I feel AWS offers a robust and versatile platform for cloud infrastructure and services. It's scalability, reliability array of tools make it a top choice for businesses of all sizes. AWS has better open source communities such as Linux, Jenkins and GitHub in comparison to Azure service cloud
We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.