4 ms·
No mention of App Engine, Elastic Beanstalk, IBM Bluemix, Microsoft Azure, Cloud Foundry, Parse, Firebase. The only company I recognize from that list is Heroku
by arihant 11y ago
No mention of App Engine, Elastic Beanstalk, IBM Bluemix, Microsoft Azure, Cloud Foundry, Parse, Firebase. The only company I recognize from that list is Heroku.
If you do not even talk about market leaders in a space, you're almost guaranteed to form an inaccurate opinion.
That said, if the point he is trying to make that newcomers aren't there or aren't innovating, that's wrong too. PaaS is not moving at the slow rate that traditional hosting went through. So the term Gartner defines goes out of date before they publish their reports. There has been plenty innovation by Parse, Firebase, Compose, Mongo in 2015. IBM Bluemix came to the scene with great modularity and Watson as a service. Google brought in a bunch of new stuff too. Docker didn't kill PaaS, that's like saying LAN wires killed servers. It just pushed the level of abstraction in PaaS a bit higher. Being able to throw code and being able to run it without thinking of hardware is a very 2014 problem for most people. The sex is in what's coming next. PaaS has evolved.
- discodave 11y agoAlso, is AWS Lambda PaaS? Or something else?
- nostrademons 11y agoLambda is something new. It's akin to BaaS (backend-as-a-service, like Parse or Firebase), but operates fairly differently from them, and doesn't have the mobile focus. Not sure if I'd lump it under BaaS or if it's an entirely new category (EaaS, execution-as-a-service?).
- krakensden 11y agoHow is it something new? It seems a lot like App Engine to me, albeit with less tooling.
- nostrademons 11y agoThe interface to the outside world is different, the granularity of abstraction is different, and the pricing model is different. All those make it suitable for different applications, which indicates it's a new market and not going after the same customers as a PaaS. AppEngine still treats your whole codebase as an "app" - all your handlers share configuration, they share a data store, and you interact with them over straight HTTP or XMPP. You're billed per instance-hour, which implies instances (virtual machines), and the control panel is setup to scale the number of instances devoted to your app. Lambda is just a collection of functions, and you setup those functions to be triggered on various events. Those events could include HTTP requests to an API gateway, but they also include S3 or DynamoDB writes, Cloudwatch monitoring, SNS, and a wide variety of other apps. You're billed only for computing time; having an Amazon Lambda function uploaded that's doing nothing costs you nothing. I get the sense that Amazon Lambda : database triggers :: Google AppEngine : webapps. The former is utility code that glues together events in multiple storage systems; the latter is designed to serve a single application and interface with all of its data needs.
- csears 11y agoYou can pair Lambda up with AWS API Gateway and get something pretty close to App Engine. What sets Lambda apart is that it is event activated, similar to stored procedures in a database. But instead of updates or inserts to tables, Lambda can be triggered by events in other AWS services (S3 object created, API gateway method requested, etc).
- EwanToo 11y agoto me it's PaaS - sure it's fairly limited today, but it's expanding it's functionality at a massive rate
- olalonde 11y agoAnd Deis, Kubernetes, CoreOS/fleet, Tutum, etc.
- stickfigure 11y agoFurthermore, the measure of PaaS is not whether PaaS companies are profitable, but whether the companies built on PaaS systems are profitable. Infrastructure should be a tough business. As a startup developer, I want them pouring every extra cent into either expanding my services or making my existing services cheaper.
- ibotty 11y agoThere is also RedHat's openshift that got rebuild on top of kubernetes and is alive and striving.
- toddmorey 11y agoAlso, Pantheon seems to be doing very well as a PaaS for Drupal and WordPress.