Interesting insights until you realize that the author has a not so hidden agenda for posting such an article.
Why did Facebook decide to shut down Parse?
31–40 of 89 posts
Re: Why did Facebook decide to shut down Parse?
#32>Can you trust your platform of choice, or will they close shop on you tomorrow?
I'm thinking about moving to IBM BlueMix with parts of my business and asking myself the same question. What do you guys think? Will BlueMix still be there in a couple of years (3,4)? I know nobody using it, but IBM is promoting it quite aggressively, and it makes sense for me to have an alternative for both self-made AWS clusters (IaaS) AND BaaS like Parse.
Re: Why did Facebook decide to shut down Parse?
#33There's also http://www.28.io (totally ungooglable name, btw. Also know as "28msec").
http://www.28.io/documentation/latest/data-sources/
Not really comparable to Parse, even though they call it "Virtual Databases". Sure, you can query everything, but what about updates?
EDIT: Looks like they have updates, but I couldn't find whether they support similar uniform interface to updates as they have for queries (ideally XQuery Update Facility).
Re: Why did Facebook decide to shut down Parse?
#34This "article" is just an ad, once you reach the last paragraph.
Pretty much. It's fitting in with the trend of execs writing about buzzwords to make the topics relevant to their startup offering.
Re: Why did Facebook decide to shut down Parse?
#35Earlier quoted context omitted.
I think most developers are wary about putting their company's tech stack at the mercy of a profit-driven company that may abandon them. Heroku? Salesforce bought them, still going, still very heavily used.
IMO: Heroku is a bad example of vendor lock in. To use Heroku, no code changes were required which would prevent it from running else where. A counter-argument to my counter-argument, Heroku limitations (i.e. 30-second HTTP request timeouts) required code changes for any and all web apps to work on Heroku. Anyhow, code that runs on Heroku can run anywhere. Parse, on the other hand, was both the code and the infrastru…
> Heroku limitations (i.e. 30-second HTTP request timeouts)
I see this as less of a limitation and more as Heroku forcing you to write your app in a scalable manner. Likewise with Heroku servers/dynos not coming with permanent storage and not letting you SSH into them.
Re: Why did Facebook decide to shut down Parse?
#36Parse never made sense to me. I could see a service like Parse being useful, but it would need to be owned / operated by a nonprofit in order to gain any adoption. Otherwise, it's just another proprietary platform that will get shut off or changed once Facebook (or whoever) pivots to another business model to address that market. There's certainly demand, but I think most developers are wary about putting their compa…
It didn't make sense to me until I had a.) started a company and b.) saw the historical tech stacks of a number of companies (eg. Google, Facebook, EBay) that had hit it big. I started my career with the belief that your company has one tech stack, the chief architect chooses it when the company is founded, and that you never ever rewrite it because you're in for a world of pain if you do. I learned that basically no…
I was nodding so much to this comment. Been there, done that. Been on both sides.
Re: Why did Facebook decide to shut down Parse?
#37Parse never made sense to me. I could see a service like Parse being useful, but it would need to be owned / operated by a nonprofit in order to gain any adoption. Otherwise, it's just another proprietary platform that will get shut off or changed once Facebook (or whoever) pivots to another business model to address that market. There's certainly demand, but I think most developers are wary about putting their compa…
It didn't make sense to me until I had a.) started a company and b.) saw the historical tech stacks of a number of companies (eg. Google, Facebook, EBay) that had hit it big. I started my career with the belief that your company has one tech stack, the chief architect chooses it when the company is founded, and that you never ever rewrite it because you're in for a world of pain if you do. I learned that basically no…
Did facebook move away from PHP ? Did google radically switch stacks ?
Re: Why did Facebook decide to shut down Parse?
#38Parse never made sense to me. I could see a service like Parse being useful, but it would need to be owned / operated by a nonprofit in order to gain any adoption. Otherwise, it's just another proprietary platform that will get shut off or changed once Facebook (or whoever) pivots to another business model to address that market. There's certainly demand, but I think most developers are wary about putting their compa…
It didn't make sense to me until I had a.) started a company and b.) saw the historical tech stacks of a number of companies (eg. Google, Facebook, EBay) that had hit it big. I started my career with the belief that your company has one tech stack, the chief architect chooses it when the company is founded, and that you never ever rewrite it because you're in for a world of pain if you do. I learned that basically no…
The circle of life-cycles. Turn it into a diagram and help founders, early employees, VPs and managers to navigate these phase transitions.
Re: Why did Facebook decide to shut down Parse?
#39Parse never made sense to me. I could see a service like Parse being useful, but it would need to be owned / operated by a nonprofit in order to gain any adoption. Otherwise, it's just another proprietary platform that will get shut off or changed once Facebook (or whoever) pivots to another business model to address that market. There's certainly demand, but I think most developers are wary about putting their compa…
It didn't make sense to me until I had a.) started a company and b.) saw the historical tech stacks of a number of companies (eg. Google, Facebook, EBay) that had hit it big. I started my career with the belief that your company has one tech stack, the chief architect chooses it when the company is founded, and that you never ever rewrite it because you're in for a world of pain if you do. I learned that basically no…
your second paragraph would be incredibly unfortunate. most of the sane large companies i've worked at or know people who work at have settled on 2-4 languages -one of which is usually the legacy starting language-which they provide tier-1 support through dedicated teams providing "the stack" in various forms. everything else is community owned and caveat emptor. its why startups should be able to use whatever language they use a selling point; a huge company churning through languages du jour sounds like an awful experience.
Re: Why did Facebook decide to shut down Parse?
#40Yeah, it sucks Parse shut down. But that's not an argument to avoid SaaS. My startup is built on over 20+ different third-party tools. It will really, really suck if any of them shut down... but I'd rather deal with that possibility in the future when we have more money and time, than struggle to build everything out ourselves now. Like I said, it sucks Parse is shutting down. But in ~2 hours, you can get the open so…
> in ~2 hours, you can get the open source Parse clone they released going and be back to new I keep hearing this, and I have a hard time believing it. Are there any examples of a significant app/developer doing this? Sure a working Parse Server is easy to get up and running, but the reason someone wouold choose Parse was to avoid operations, and that's not a service you build in your company in 2 hrs. (as an aside,…
If you have a small app and don't need to be careful about scaling issues, then 2 hours is pretty accurate I think. It's trickier when you have a large app, because with Parse Server you do need to handle your own databases and production environment. So I think some of the larger apps are either going to need to hire some devops folks, or make an arrangement with higher-service providers like ObjectRocket.
It has been less than a week, though, so we will see.