- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
LinkedIn Architecture
Created by bagwell on 2010-10-12.
Updated: 2010-10-12, 12:31
You may enjoy to read about the architecture behind the highly successful LinkedIn services used by millions of people. Dionysios G. Synodinos at InfoQ has been talking to the technical people behind it all, Alejandro Crosa, Chris Conrad and Jay Kreps. They describe the architectural decisions, trade-offs and the benefits of bringing Scala into the equation and how it all plays together with JRuby and back-end databases. Alejandro is clear about Scala, "If you use Scala just like you would use Java then you are just getting a more succinct syntax and nothing else. Embrace immutability, functional data structures, pattern matching, Actors, etc. and you'll never go back."
- Login or register to post comments
Printer-friendly version
Re: LinkedIn Architecture
Just a gentle reminder that it is always best to be inclusive when building a community. Some new Scala users may well be at the level where they use Scala just like a more succinct Java. We should make them feel welcome.
How about "When you transition from Java to Scala, an immediate benefit is a more succinct syntax. But there is so much more: embrace immutability, functional data structures, pattern matching, Actors, etc. and you'll never go back."
Re: LinkedIn Architecture
cayhorstmann you are being *too* sensitive, your text change is almost the same, my intent was not to sound like that. I find myself writing code that's just "a succint improvement" a lot of times, and try to improve it later.
Words don't make a community more inclusive or not, actions do, showing people how to use scala, answering questions, doing talks, meetups, etc.