Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Your Application is *Not* Lightweight If

DZone's Guide to

Your Application is *Not* Lightweight If

· Java Zone ·
Free Resource

How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

  1. You already know what ThreadLocal is (and used that extensively)
  2. You see transaction management in the application code (an annotation, however is not perfect, but o.k.)
  3. You have to deal with EntityManagerFactory and EntityTransaction in your code
  4. Your XML-configuration doesn't fit on a single page any more
  5. Your solution cannot be handled without extensive tooling
  6. You spend some time for convincing other developers, that your solution is actually lightweight :-)
  7. You are in the process of replacing existing frameworks with your "lightweight" POJOs and hope the result will be easier, lighter and better maintainable
  8. You forgot the name and purpose of the layers
  9. The number of interfaces is equal or greater, than the number of classes, and you need naming conventions to deal with that
  10. The deployment size of your application archive (WAR) is greater, than the installation size of your "lightweight" server (like tomcat)
From http://www.adam-bien.com/roller/abien/entry/your_application_is_not_lightweight

How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}