What is Clever Cloud?
What is Google App Engine?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Google App Engine?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We have recently moved our Playframework app to Clevercloud. It was relatively painless and the few issues we did have was mostly of the RTM type.... in fact, everything came down to minor configuration tweaks on our side... the Clevercloud stack performed flawlessly throughout.
The Clevercloud team doesn't have a moat of "Level 1 Support" people around their technical experts, who try to fob off support queries with canned responses, like a lot of other hosting companies do.... when you have a technical question it gets answered by a member of the core engineering team, pretty much straight away. They are knowledgeable, think out the box and are willing to entertain non-standard requests (within reason).
The platform is accessible via a web-based console or a custom CLI. Both are easy and straightforward to use. Changing your scaling strategy (vertical, horizontal or both) is dead simple, as are deployments (git push). We don't use Github, but I understand things are even easier if you do. The infrastructure also seems quite robust (a little early to tell for sure) and is certainly performant.
For us as primarily software developers who do server admin, etc. mostly in self-defence, the Clevercloud platform and team is heaven sent. It's like having your own data centre, run by your own team of dedicated devops ninjas... at a fraction of the price and none of the HR issues 😄
I adopted node.js the year it came out. I have hosted my experimental and general purpose sites on many cloud hosting services, including ones that don't exist any more.
Clever Cloud has been by far the best experience yet. There was a brief, steep learning curve, but I had excellent personal support from Quentin himself and several other excellent techs.
I have high confidence in this service and I will recommend it to my associates and expect to deploy large scale sites soon. All I can say is good job and well done! They do everything right, and its a breeze tracking and controlling many sites.
I work as a freelancer and I'm used to pick the right tool for the right job. As a result I have projects in Node.js, Play framework, JEE with multiple DB engines (postgresql, mysql, couchbase, mongodb)… Using a PaaS with native support of these stacks make me save lots of time. I can also setup beta environments to share ongoing work with my clients before prime-time. Deployment fits well in my workflow (git push). The blue-green deployment process saved my ass several times when I needed to deploy fixes during a surge of traffic.
The support is quick to answer and takes feedback into account.
I use Heroku, for almost any project of mine. Their free plan is awesome for testing, solo developers or your startup and its almost impossible to not cover you somehow. Adding an add on is a simple command away and I find it easy to use it both on my Windows PC or my Linux laptop. Their documentation, covers almost everything. In particular I have used Heroku for Spring, Django and AngularJS. I even find it easier to run my project on my local dev with foreman start, than ./manage.py runserver (for my django projects). There is no place like Heroku for the developer!
The platform is really easy to use, everything works as expected, no surprise. The first app I deployed was a Spring Boot app; in less than an hour, I've been able to write the hello world app, subscribe and deploy.
The pricing is fair, and you pay for your use only (no hidden cost such as app storage or something like that).
And the biggest point: the support is awesome. If you miss something, just ask: they will give you the help you need.
To sum up: give a try, and I'm pretty sure you will never go back.
We use clever to host a CRM and everything is cool in my experience; a lot of tools to deploy in a few clicks, MySQL ? 2 clicks. A web app for your CMS ? 3 clicks. Deploy a new version? 1 git push.
Just easy to setup, easy to maintain, easy to engage new developer on this stack, and if you need some help, ping them and see how fast your question we be answered, at night, on weekends...
OH, and your know what? It just works all the time, and pricing is fair.
Guys: You Rocks !
Can't beat the simplicity of deploying and managing apps, the pricing is a bit high, but you are paying for those streamlined tools. However, after several experiences of tracing issues back to Heroku's stack, not having visibility into what they are doing has prompted moving two applications off of it and on to other more transparent cloud solutions. Heroku is amazing for what it is, hosting for early stage products.
With Cloud Endpoints you can create and deploy mobile backend in one hour or less. And it is free (until you need extra scale). I would not recommend to use Java - python is faster and has all new appengine features.
Pros: everything is in one place: task queue, cron, backend instances for data processing, datastore, mapreduce. Cons: you cannot easily move your code from GAE. Even with special 3rd party services.
I've been using Heroku for 3 years now, they have grown super fast and each time they're improving their services. What I really like the most is how easily you can show to your client the advances on you project, it would take you maximum 15 minutes to configure two environments (Staging/Production). It is simply essential and fantastic!
I liked how easy this was to use and that I could create some proof of concepts without have to pay. The downside for NodeJS is remote debugging. Pretty much have to depend on logging where Azure allows remote debugging with Node Inspector.
Using Heroku takes away all the pains associated with managing compute and backing services. It may require a little extra optimisation and tweaks, but these constraints often make your app better anyway.
With Cloud Endpoints you can create and deploy mobile backend in one hour or less.
Not having to deal with servers is a huge win for us. There are certainly trade-offs (having to wait if the platform is down as opposed to being able to fix the issue), but we’re happy being on Heroku right now. Being able to focus 100% of our technical efforts on application code is immensely helpful.
Two dynos seems to be the sweet spot for our application. We can handle traffic spikes and get pretty consistent performance otherwise.
We have a total of four apps on Heroku: Legacy Leanstack, StackShare Prod, StackShare Staging, StackShare Dev. Protip: if you’re setting up multiple environments based on your prod environment, just run heroku fork app name. Super useful, it copies over your db, add-ons, and settings.
We have a develop branch on GitHub that we push to dev to test out, then if everything is cool we push it to staging and eventually prod. Hotfixes of course go straight to staging and then prod usually.
PaaS for back-end components, including external data ingestion APIs, front-end web service APIs, hosting of static front-end application assets, back-end data processing pipeline microservices, APIs to storage infrastructure (Cloud SQL and Memcached), and data processing pipeline task queues and cron jobs. Task queue fan-out and auto-scaling of back-end microservice instances provide parallelism for high velocity data processing.
checking a swap require a lot of cpu resource, roster normally come out same day of month, every month, at a particular time. Which make very high spike, our flag ship product, iSwap, with the capability looking swap possibility with 10000 other rosters base on user critieria, you need a cloud computing give you this magnitude of computing power. gae did it nicely, user friendly, easy to you, low cost.
Heroku runs the web and background worker processes. Auto-deployments are triggered via GitHub commits and wait for the Buildkite test build to pass. Heroku pipelines with beta release phase execution (for automatically running database migrations) allowed for easy manual testing of big new releases. Web and worker logs are sent to Papertrail.
As much as I love AWS EC, I prefer Heroku for apps like this. Heroku has grown up around Rails and Ruby, massive set of add-ons that are usually one-click setup, and I once had to perform an emergency app scale-up a that I completed in seconds from my mobile phone whilst riding the Bangkok subway. Doesn't get much easier than that.
Used for proofs of concept and personal projects where I want to remain in a free tier (as opposed to a service like DigitalOcean), and application state must outlive an HTTP request/response cycle.
Heroku Postgres sometimes used as a free tier PostgreSQL managed database linked to non-Heroku apps, for example AWS Lambda.
App engine fills in the gaps in the increasingly smaller case where it's necessary for us to run our own APIs.
Very easy to make cloud computing of ML models , and use containers like Kubernetes.