3. contact@alibassam.com ali-bassam
1- Fat Applications
● One single big fat source code
● Front-end and Back-end are combined
● Each developer clones the complete source code in order
to work
● Difficult to maintain, hundreds of classes, packages and
libraries
● New Developers: “This is fat and scary!”
● => lower productivity and higher frustration
3
5. contact@alibassam.com ali-bassam
1- Fat Applications
● As the number of users/customers increase, scaling is
difficult
● Usual solution is to scale up, get a better hardware
● If there’s a small bug, the whole application is taken
down, a new deploy is required
● Upgrading language/framework or application server is
difficult
5
7. contact@alibassam.com ali-bassam
2- Fit & Sexy Applications
● Decomposition of the application into smaller pieces
● Each piece can function on its own. Exclusive business
capability
● Communication between pieces via well-defined interfaces
(HTTP/REST) - Always Stateless
● Independent life cycle (development teams, technology
choices, not held back by other pieces)
● ⇒ Loosely Coupled system, if one piece is dead, the
system isn’t dead
7
9. contact@alibassam.com ali-bassam
2- Fit & Sexy Applications
● Instead of scaling the entire application, scale only the
microservice with higher traffic
● Ready for the cloud
9
14. contact@alibassam.com ali-bassam
4- Diet Plan
● Focus primarily on business when decomposing the fat
application
● Begin with the parts that has the least or none
dependencies
● Only use HTTP (REST/SOAP) and keep it stateless
● Separate the UI
14
16. contact@alibassam.com ali-bassam
5- Conclusion
● Having a healthy lifestyle should be our number one
priority
● As obesity is on the rise, it is crucial to stick to a
healthy diet plan
● Being fit, helps us move easier and remain attractive
● Being fat, increases the risks of health problems
16
