Google App Engine vs. Nexthink

App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.

Incentivized

I've been managing desktops for 20+ years and Nexthink was the missing tool out of my toolbox. Just to give some perspective, if you were building and maintaining a house, Nexthink would be comparable to switching up from a hammer and nails and to full blown using a nailgun. Nexthink is a solution accelerator and a well thought out toolset to give you the customer experience at a glance. It allows for so much more visibility just with the default set of data points the Collector (agent) gathers, which is A LOT, and grants you the ability to gather even more data with remote actions. All of this evidence cuts how the "it could possibly be this" and "maybe it's that" discussions when you're troubleshooting an issue. It may not provide the exact answer all the time, but it gives you a "compass point" on where you need to start looking to resolve the issue. Also the service monitoring, activity monitoring, and critical event thresholds really empower the teams to know when a problem is happening and they can get ahead of it before the first call even reaches the Help Desk. Nexthink is a cornerstone tool in our environment for end user experience and I'm excited to see where the go next.

• Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
• Flexible. We use Java for some services and Node.js for others.
• Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.

Incentivized

• It allows for an IT department to be proactive with finding/solving issues before they happen
• It allows for a company to have a great tool for engaging with end users using campaigns/surveys
• It shows the full overall picture of a device/network connections when troubleshooting user issues.

• There is a slight learning curve to getting used to code on Google App Engine.
• Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
• Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)

Incentivized

• The on-premise solution can be slow at times and resource-demanding even on newer laptops. (This isn't the case with the cloud offering.)
• Some useful features are only available to cloud customers.
• Library pack configuration could be made easier, often these packs require some customization and it's not always clear how to get them up and running after importing.

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.

Incentivized

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

Incentivized

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.

Incentivized

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 compared to the other major players in Azure and AWS.

Incentivized

Nexthink had better integration and a better user interface. 1E did not have the engagement capability which is so critical to many of the actions we complete using Nexthink. Nexthink had better trending data capabilities. 1E did not capture and hold data the way Nexthink does so all data assumes you are able to pull information from all systems at any time. with remote systems it is unlikely you will capture all systems at the same time so it makes any actions less effective. this review was performed 4 years ago so 1E may have addressed some of these limitations but Nexthink has also grown and continues to add and improve on their industry-leading capabilities.

Incentivized

• Effective employee adoption through ease of use.
• Effective integration to other java based frameworks.
• Time to market is very quick. Build, test, deploy and use.
• The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.

Incentivized

• SCCM proactive remediation: Automatically resolving hundreds of SCCM issues per month
• Hardware: Identification of over $5m cost avoidance by seeing a lack of usage for 128GB SSDs - no need to upgrade to 256GB... coupled with OneDrive migration packs in the Nexthink library this is valuable.

Incentivized