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
Salesforce Lightning Platform
Score 7.7 out of 10
N/A
Salesforce Platform is designed for building and deploying scalable cloud applications with managed hardware provisioning and app stacks. It provides out-of-the-box tools and services to automate business processes, integrate with external apps, and provide responsive layouts and more.
$25
Per User Per Month
Pricing
Google App Engine
Salesforce Lightning Platform
Editions & Modules
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Starter
$25.00
Per User Per Month
Plus
$100.00
Per User Per Month
Offerings
Pricing Offerings
Google App Engine
Salesforce Lightning 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
Google App Engine
Salesforce Lightning Platform
Considered Both Products
Google App Engine
Verified User
Anonymous
Chose Google App Engine
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…
Google App Engine stands out since it offers everything as being a platform as a service. The other options I used before, such as classical development with servers available either in house or in the cloud still require a lot of management and the software frameworks …
Salesforce Lightning Platform provides a more sales-focused CRM. It allows the sales force of an organization to be able to stay organized and can pull necessary reports to get a better understanding on how the business is performing regarding sales and customer activity. …
Salesforce stands out purely for its enterprise pedigree. No other competitor out there knows Enterprise business as well as Salesforce does. It is levels about the rest of the competition in terms of managing heavy processing requirements of a large enterprise. I did not have …
Compared to Sage CRM, Salesforce Lightning Platform is leaps and bounds ahead. Sage CRM feels outdated and very slow compared to Salesforce Lightning Platform. There is a lot more ability to integrate Salesforce Lightning Platform with other APIs and systems. There is more of …
I have been using Salesforce for two years now. Ans I have not used any other platform before similar on this. I find Salesforce very easy to use and this really makes your job much easier and faster. Its features are easy to understand and use and I am glad I have learned …
We have always been a Salesforce shop, but have grown with the App Cloud platform as it's evolved. We eventually moved to lightning based on the streamlined interface and increased ease of use for our employees. So far we are happy with the results. Would definitely recommend …
Salesforce, while more expensive, provides faster support, higher scalability options, and an increased opportunity to change any details whether it's about user permissions management, custom field or object creation, or an integration of another application. What really sets …
Salesforce has more functionality as a CRM platform. The major disadvantage is the ability to integrate with Microsoft products. Ability to integrate with Microsoft is the best part about 356 given that it is a Microsoft product. Even though the price is more expensive, it …
Director Of Business Development - Operating Room, Vein Therapy, Personal Protective Equipment (PPE)
Chose Salesforce Lightning Platform
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. …
I think Salesforce has the most powerful developer engine - I have yet to need a module that I couldn't create (maybe with help). I probably could have made the others work but Salesforce, in my opinion, made it the easiest. Salesforce is reliable and established as well so …
I would love to switch back to Service Cloud as it was much, much more intuitive and fast. I would even take Salesforce Classic over Lightning. It at least wasn't this slow.
I used a program formerly known as "CP." I considered it somewhat outdated, and it does not have any of the modern features that the Salesforce Lightning Platform (formerly Salesforce App Cloud) has. I consider the Salesforce Lightning Platform (formerly Salesforce App Cloud) …
I use both. SF is the constant through the organization and I receive leads into SF and pass on opportunities through SF. SL is better for internal processes within business dev.
Salesforce is the premeire product. Period. The others are cheaper and less capable, they may fulfill your organisation's needs but you will always be looking at Salesforce with wishful eyes. If you are a company that needs to bootstrap then spend the time to evaluate your …
Microsoft is pretty limited in functionality compared to Salesforce. Most folks coming into your organization are going to have some level of Salesforce experience but will most likely not have experience with Dynamics. Dynamics doesn't connect as well to other platforms.
I believe the only reason we didn't choose Monday.com is because we're just a bit bigger (company size- 75 people) than what Monday.com handles. We also are in San Francisco, and Salesforce pretty much owns this entire city. I was also not part of the selection process of the …
There is a reason why the Salesforce Lightning Platform is the market leader for all things related to customer relationship management. While Close is somewhat user-friendly, it pales in comparison to all the features, bells, and whistles that the Salesforce Lightning Platform …
We originally used spreadsheets when we first started. That worked fine until we started growing by over 100% year over year. We were able to upload all of our previous accounts in Salesforce Classic once it was called for. However, Salesforce Classic soon became redundant and …
We needed a product that would allow for easy and dynamic reports for potential and new clients. Account Managers use other products as well to monitor the client's success and Salesforce allows for seamless integration to other platforms. This serves as a one-stop-shop for all …
We currently use the two together, along with Hubspot sales. Salesforce is our primary CRM and where we track and manage account and contact information. Salesforce is much more flexible and intuitive - everything is where you would expect it to be. Hubspot reporting is …
I think that the Lightning platform is not as clean and doesn't integrate that well. Whenever I was logged out, it was such a treck to have to log back in and I never actually knew if my activity was being saved or actually being tracked. Personally, Lightning is not my …
Close and Salesforce are two very different beasts. Close is much more user friendly but lacks the ability to serve complex infrastructures and hierarchies provided by Salesforce. Close is much simpler and faster--great for high volume but will not provide you with rich, …
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.
We use Salesforce Lightning Platform in everyday business as sales coordinators. By using this tool, we are able to send new requests to clients and communicate regarding pending proposals in real-time. This also tool holds many of our client accounts where we are able to monitor their sales and revenue.
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.
Reporting and Dashboards are thorough and can show a wealth of important data to inform and scale processes. It's helpful in a high volume sales cycle to be able to quickly identify weak points in performance and productivity so that adjustments can be made.
Highly customizable. We are able to customize just about everything which allows us to track very specific things and in theory create better efficiency.
Parent/Child account hierarchy exists which is helpful.
Contact records can be associated with multiple accounts and opportunities. This, in theory, should minimize duplicates and mismanagement of contacts.
Console helps a lot with data nesting. Having a fairly comprehensive look at an account without searching through various tabs and sections speeds up an otherwise cumbersome platform.
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.
Google App Engine is very intuitive. It has the common programming language most would use. Google is a dependable name and I have not had issues with their servers being down....ever. You can safely use their service and store your data on their servers without worrying about downtime or loss of data.
UI can be quite complex, but the more that is required will bring more complexity. Can handle complexity and variety very well, but makes ground-level views harder when not knowing full extent of functionality. Finding new functionalities can be difficult to pinpoint on some pages
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.
Salesforce's support is top-notch. They have subject-matter experts that are accessible at all times to address needs as they come up. They let you know in advance when there are system updates and enhancements so that you are prepared for upcoming changes. I've never had an issue that wasn't addressed immediately when reaching out for support.
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.
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.