4 ms·
Open Sourcing the App Engine Standard Java Runtime
- skybrian 5y ago> Finally, being able to compile, test and release the Java runtime environment for Java 8, Java 11 and soon Java 17 from an open source platform is much easier than relying on the huge internal Google mono repository system which is intended to support only one single version of everything, including a single JDK toolchain. The maintainers of Java in google3 probably like this simplification a lot too.
- klabb3 5y agoI was on the GAE team several years ago and I'd be really surprised if they moved source-of-truth out of google3. They would need massive infrastructure reorgs in order to make that happen, on a product that is very difficult to staff because of tech debt and new shiny things nearby. I bet this is "just" a public mirror (which doesn't mean it wasn't a big effort).
- splix 5y agoGoogle App Engine was a really great advance in building scalable web apps. Used it since the very first days and loved it. Still have a couple of projects running on App Engine. Remember when I launched my first project on App Engine, it was noticed by a local radio station, and it just proved to me that the scaling technology just works. 100x traffic jump, easy handled like nothing happened.
- Jyaif 5y agoApp Engine is hosting for programmers that do not want to deal with administrating servers. For me it's really perfect, and there's nothing quite like it.
- nocommandline 5y agoFull disclosure - I have an App (GUI) for App Engine. I fully agree with you. a) Want to force people to sign in to access your app? Slap a `login:required' in app.yaml or use the 'users Api' b) Want to serve different image sizes? Use the 'Images' API to get a url and add a size as a parameter c) Want to search your data (imagine you have a shopping site and you want folks to search your product)? Use the 'Search API' I don't have to tinker with any server. Just write code and deploy it. Another thing I loved about GAE GUI (which is part of the reason I built a replacement GUI when they deprecated theirs) is that it was easy to get 'new' or 'inexperienced' programmers up and running on the web. Click a button and your code gets transferred to Google. Click a button and your code runs locally
- leonidasv 5y agoThis is another sign that App Engine is slowly being discontinued. Google seems to be moving towards Cloud Run and Cloud Functions as the default solution for scaling apps without hassling with Kubernetes. Although I do like Cloud Run (and Functions, to a lesser extent), App Engine has (had?) some useful features that are not present on those offerings. What I miss the most is the async worker/background jobs feature. Cloud Run/Functions forces you to use HTTP requests for everything (Functions has some exemptions for a handful of triggers), leaving some use cases unattended. If you have some long-runnning job, you are stuck with HTTP requests with long timeouts and that's it. I really hope this gets addressed in the future, will simplify things a lot for smaller businesses/solo projects. For example, at my company, we decided to move large parts of our infrastructure to Kubernetes (hosted at GCP). The lack of an elegant solution for background jobs in Cloud Run was the major reason for this decision, otherwise we would have just continued using it for the time to come.
- steren 5y agoCloud Run can be configured to have CPU always allocated, whcih allows for background processing. By combining this with a number of minimum instances, one can benefit from always on instances, not request driven, to execute background jobs
- leonidasv 5y agoWow, this is new. Last time I had checked this option wasn't available. Thanks for pointing this out. Although it seems it won't scale automatically for background processing, a clever setup with some alarms may have a decent mileage. Nice to know.
- riddleronroof 5y agoYeah. It’s new. They added it to allow web sockets, amongst other things.
- aitchnyu 5y agoCan a single CR service execute requests as well as background tasks? And can requests and tasks have separate timeouts?
- webmaven 5y agoThe Python equivalent is in preview: https://github.com/GoogleCloudPlatform/appengine-python-standard https://github.com/GoogleCloudPlatform/appengine-python-stan...
- ChicagoBoy11 5y agoI learned web development through Steve Huffman's Intro to Web Dev course which used app engine. It was incredibly powerful and it did a great job in allowing you to focus on what really mattered. Definitely thankful for whomever maintained the project; it was instrumental in allowing me to build my skills as a developer.
- mmastrac 5y agoAs a heavy user of AppEngine/Java in the early days, I don't think AppEngine/Java was every really viable. The long, long startup times were absolutely brutal for scaling (30s-1min+, even w/ridic. work to optimize). I stopped using it ~2014, but at that point it felt like it was going to go anywhere at all. The AppEngine environment just needed ways to pre-warm/pre-JIT (or even a snapshot function) to make this feasible on the underpowered instances that used to run it. I also used a ton of AppEngine/Python (and still do on some of my personal single-serve sites - ie progscrape.com) and that was just so much better overall. Given the heavy use of caching, none of my AppEngine/Python sites ever incur a bill of >$0.10 per month.
- matthewmorgan 5y agoCan't google afford a native speaker to proof read their text output?
- warkdarrior 5y agoGPT-3 told Google with high confidence that the text was fine. :)