You probably know that Netflix is really just about RxJava microservices, with Hystrix and Spring Cloud. Really, Chaos Monkeys are just running the show. Paul Bakker discusses Netflix’s use of Java, emphasizing the use of microservices, RxJava, Hystrix and Spring Cloud. By @infoq.com.
The main problem is really that reactive is just really hard. Speaking for myself, I’ve been doing reactive programming for at least 10 years. I used to be extremely excited about it, and tell everyone about how great it all is. It is actually hard, because even if with that experience, look at a non-trivial piece of reactive code, I have no clue what’s going on. It takes me quite a bit of time to actually wrap my head around, ok, this is actually what’s happening. These are the operations that are supposed to happen.
Main points mentioned in discussion:
- Evolving architecture
- The groovy era
- Limitations
- GraphQL federation
- What does that mean for our Java stack?
- The micro in Microservices
- Java at Netflix
- Virtual threads
- Spring Boot Netflix
- DGS Framework
Comparing GraphQL to REST, one very important aspect of GraphQL is that with GraphQL, you always have a schema. In your schema, you put all your operations, so your queries and your mutations, and you define them, and you tell it exactly which fields are available from the types that you’re returning from your queries. Link directs you to vide presentation and transcript. Super interesting!
[Read More]