Chapter 14. Case studies, part 1
This chapter covers
- Droplr
- Firebase
- Urban Airship
In this chapter we’ll present the first of two sets of case studies contributed by companies that have used Netty extensively in their internal infrastructure. We hope that these examples of how others have utilized the framework to solve real-world problems will broaden your understanding of what you can accomplish with Netty.
Note
The author or authors of each study were directly involved in the project they discuss.
Bruno de Carvalho, Lead Architect
At Droplr we use Netty at the heart of our infrastructure, in everything from our API servers to auxiliary services.
This is a case study on how we moved from a monolithic and sluggish LAMP[1] application to a modern, high-performance and horizontally distributed infrastructure, implemented atop Netty.
1An acronym for a typical application technology stack; originally Linux, Apache Web Server, MySQL, and PHP.
When I joined the team, we were running a LAMP application that served both as the front end for users and as an API for the client applications—among which, my reverse-engineered, third-party Windows client, windroplr.
Windroplr went on to become Droplr for Windows, and I, being mostly an infrastructure guy, eventually got a new challenge: completely rethink Droplr’s infrastructure.