4 ms·

I have no idea what Apollo Graph QL is, but it was interesting to search by URL and see the progression of related HN titles and their engagement. 2018 July. A

I have no idea what Apollo Graph QL is, but it was interesting to search by URL and see the progression of related HN titles and their engagement. 2018 July. Apollo server 2 released woo! (mostly ignored) 2019 Feb. We switched away from Slack woo! . . . (Some PRs everybody ignored) 2019 June. We got a $22M investment woo! . . . (Many PRs everybody ignored) 2022 Dec. Oops, we are laying of lots of people...

SketchySeaBeast 4y ago
Their HN may have been ignored, but both of the last two companies I've worked with have both used Apollo.
alexchamberlain 4y ago
Outside of Facebook, Apollo is _the_ GraphQL company, with innovations in the federation space in particular.
- benatkin 4y ago
  Why use GraphQL? There is tRPC now.
  - satvikpendem 4y ago
    I use GraphQL because my clients are not all TypeScript based. Also I don't necessarily want to write my backend in TypeScript either. My stack is therefore Rust with GraphQL with clients in React for web and Flutter for mobile.
  - reducesuffering 4y ago
    tRPC is for a single team working on Typescript frontend to Typescript backend (that's niche). If you have native mobile clients (different lang) or different teams that need to agree on a contract (GraphQL schema), GraphQL is the recommendation, even from ardent tRPC supporters.
    - benatkin 4y ago
      Yeah maybe. It's a leaky abstraction where the real magic happens in the RPCs in the "resolvers"
  - SlickStef11 4y ago
    Gonna put this article I read earlier this week in here to answer your question: https://wundergraph.com/blog/trpc_vs_graphql https://wundergraph.com/blog/trpc_vs_graphql
sergiotapia 4y ago
Apollo is synonymous with Graphql at this point. If you need you consume a Graphql API you most certainly reach out for Apollo on the clientside to query data.
- dventimihasura 4y ago
  Rubbish https://graphql.org/code/#javascript https://graphql.org/code/#javascript
- reducesuffering 4y ago
  Eh, https://github.com/urql-graphql/urql https://github.com/urql-graphql/urql is considered the improved re-architected project that doesn't contain the legacy baggage from the beginning of GraphQL like Apollo does.
  - satvikpendem 4y ago
    Urql client is great, however for the backend, Apollo Server really can't be beat, at least for a NodeJS backend.
    - dventimihasura 4y ago
      Rubbish. For the backend, Apollo Server absolutely can be beat by tools that don't require you to write any code: https://supabase.com/blog/pg-graphql https://supabase.com/blog/pg-graphql https://www.graphile.org/postgraphile/ https://www.graphile.org/postgraphile/ https://hasura.io/ https://hasura.io/
      - satvikpendem 4y ago
        Do you work for Hasura, based on your username? You've been spamming the same comment looking at your comment history. Anyway, these are all tools to generate a backend based on your database which might work for simple situations but breaks down for more complicated ones. I also don't want to give my backend away to Hasura or Supabase either.
subpixel 4y ago
The folks who made Meteor!
- no_wizard 4y ago
  I thought they were different entities? Also, big aside here, but is Meteor still a thing?
  - andrewingram 4y ago
    It spun out of Meteor, which was then sold to another org.
    - no_wizard 4y ago
      I'm interested in this history, any where I can read about all this?
      - justaregulardev 4y ago
        Here’s an article from TechCrunch (https://techcrunch.com/2019/10/02/tiny-acquires-meteor/ https://techcrunch.com/2019/10/02/tiny-acquires-meteor/) on the acquisition of Meteor by Tiny Capital
      - jpgvm 4y ago
        Read maybe not, but I was there if you are curious about anything. I was there during the transition period. Originally joined to work on the Meteor hosting platform that was called Galaxy. Handled integration of Meteor APM (which was an acquisition) both of which got sold off when the old Meteor business was sold. I then worked on what was called Apollo Optics, the GraphQL APM product. Rewrote the time series backend to port it to Apache Druid (which remains in use today!). Was somewhat unceremoniously let go of during a bad personal period. Don't think I would have stayed anyway though, main reason I stayed as long as I did was I had a really good mentor there that taught me a lot. Worth mentioning the company had already raised an absolute crap ton when on the original Meteor path, then the following pivot raised even more money. No idea how many rounds of financing the company has been through at this point but to say it exemplified the excesses of cheap money would be an understatement. Developer tools is a tough business, no-one really wants to pay for that stuff at the low end which means catering to enterprise. Long sales cycles, annoying requirements etc.
dventimihasura 4y ago
Apollo is not _the_ GraphQL company, nor is it synonymous with GraphQL. Nobody is those things.
- mfcl 4y ago
  It's just a way of saying that they are all about GraphQL. They are there for all you GraphQL needs and everything they do is related to GraphQL.

SketchySeaBeast 4y ago

Their HN may have been ignored, but both of the last two companies I've worked with have both used Apollo.

alexchamberlain 4y ago

Outside of Facebook, Apollo is _the_ GraphQL company, with innovations in the federation space in particular.

benatkin 4y ago
Why use GraphQL? There is tRPC now.
- satvikpendem 4y ago
  I use GraphQL because my clients are not all TypeScript based. Also I don't necessarily want to write my backend in TypeScript either. My stack is therefore Rust with GraphQL with clients in React for web and Flutter for mobile.
- reducesuffering 4y ago
  tRPC is for a single team working on Typescript frontend to Typescript backend (that's niche). If you have native mobile clients (different lang) or different teams that need to agree on a contract (GraphQL schema), GraphQL is the recommendation, even from ardent tRPC supporters.
  - benatkin 4y ago
    Yeah maybe. It's a leaky abstraction where the real magic happens in the RPCs in the "resolvers"
- SlickStef11 4y ago
  Gonna put this article I read earlier this week in here to answer your question: https://wundergraph.com/blog/trpc_vs_graphql https://wundergraph.com/blog/trpc_vs_graphql

sergiotapia 4y ago

Apollo is synonymous with Graphql at this point. If you need you consume a Graphql API you most certainly reach out for Apollo on the clientside to query data.

dventimihasura 4y ago
Rubbish https://graphql.org/code/#javascript https://graphql.org/code/#javascript
reducesuffering 4y ago
Eh, https://github.com/urql-graphql/urql https://github.com/urql-graphql/urql is considered the improved re-architected project that doesn't contain the legacy baggage from the beginning of GraphQL like Apollo does.
- satvikpendem 4y ago
  Urql client is great, however for the backend, Apollo Server really can't be beat, at least for a NodeJS backend.
  - dventimihasura 4y ago
    Rubbish. For the backend, Apollo Server absolutely can be beat by tools that don't require you to write any code: https://supabase.com/blog/pg-graphql https://supabase.com/blog/pg-graphql https://www.graphile.org/postgraphile/ https://www.graphile.org/postgraphile/ https://hasura.io/ https://hasura.io/
    - satvikpendem 4y ago
      Do you work for Hasura, based on your username? You've been spamming the same comment looking at your comment history. Anyway, these are all tools to generate a backend based on your database which might work for simple situations but breaks down for more complicated ones. I also don't want to give my backend away to Hasura or Supabase either.

subpixel 4y ago

The folks who made Meteor!

no_wizard 4y ago
I thought they were different entities? Also, big aside here, but is Meteor still a thing?
- andrewingram 4y ago
  It spun out of Meteor, which was then sold to another org.
  - no_wizard 4y ago
    I'm interested in this history, any where I can read about all this?
    - justaregulardev 4y ago
      Here’s an article from TechCrunch (https://techcrunch.com/2019/10/02/tiny-acquires-meteor/ https://techcrunch.com/2019/10/02/tiny-acquires-meteor/) on the acquisition of Meteor by Tiny Capital
    - jpgvm 4y ago
      Read maybe not, but I was there if you are curious about anything. I was there during the transition period. Originally joined to work on the Meteor hosting platform that was called Galaxy. Handled integration of Meteor APM (which was an acquisition) both of which got sold off when the old Meteor business was sold. I then worked on what was called Apollo Optics, the GraphQL APM product. Rewrote the time series backend to port it to Apache Druid (which remains in use today!). Was somewhat unceremoniously let go of during a bad personal period. Don't think I would have stayed anyway though, main reason I stayed as long as I did was I had a really good mentor there that taught me a lot. Worth mentioning the company had already raised an absolute crap ton when on the original Meteor path, then the following pivot raised even more money. No idea how many rounds of financing the company has been through at this point but to say it exemplified the excesses of cheap money would be an understatement. Developer tools is a tough business, no-one really wants to pay for that stuff at the low end which means catering to enterprise. Long sales cycles, annoying requirements etc.

dventimihasura 4y ago

Apollo is not _the_ GraphQL company, nor is it synonymous with GraphQL. Nobody is those things.

mfcl 4y ago
It's just a way of saying that they are all about GraphQL. They are there for all you GraphQL needs and everything they do is related to GraphQL.