DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Data Engineering
  3. Databases
  4. How to Optimize Chatty Applications

How to Optimize Chatty Applications

Sometimes, claims call the same service for the same information over and over again. This behavior is called chattiness. Caching can help us optimize this chattiness.

Abhilash Juluri user avatar by
Abhilash Juluri
·
Feb. 02, 17 · Opinion
Like (4)
Save
Tweet
Share
5.39K Views

Join the DZone community and get the full member experience.

Join For Free

You may have seen chatty applications numerous times in your career. Any app that acts as a core component in the distributed architecture has no option but to rely on other services to fulfill a request or a process. These core apps can get chatty in the early stages of their lifecycle.

Chattiness can look like this:

Image title

What is wrong with chatty apps? Calling other services to fulfill a request is all part of the plan, isn’t it?

Let’s examine chattiness characteristics with claims processing system. Before I go further, let me summarize how a healthcare claims process orchestration is (10,000-foot view).

Claims Processing Overview

Image title

Each stage above requires the claim system to make calls to other services like database, eligibility service, provider service, pricing service, business rules services, etc. Did I forget to mention fraud detection service? Oh, no!

In each stage, claims might make repeated calls to the same services based on the claim received.

Sometimes, it calls the same service for the same information over and over again! This is the behavior I’m calling chattiness. Now, what’s wrong with this behavior? One can argue that it’s a necessity to call other services and that we shouldn’t call it chattiness.

Service calls in a distributed architecture can incur many overheads including network latency, disk reads, database queries, etc. on both the caller and callee side.

How Can We Optimize This Chattiness?

Drum roll...

Caching! Yes, Caching is one sure way to solve this problem.

Caching solutions take many shapes depending on your architecture:

  • In-memory caching (i.e., Ehcache, Redis, Hazelcast).

  • Distributed caching (i.e., Oracle Coherence, Memcached)

  • Caching at API gateways or the ESB level.

Note that all the above caching solutions require robust cache refresh and replication strategies.

You may have been in environments where systems have large relational database schemas with hundreds of tables. With such large schemas, data retrieval queries get really expensive over a period of time, and the queries often require several joins, inner queries, hints, etc.

It’s a great idea to introduce a NoSQL database in between application and relational databases and stage the result sets of such complex queries, so that they will offload some load from the relational database. It’s safe to assume that this will result in a huge performance gain when you apply this solution for tables that won’t change frequently.

Conclusion

Chattiness of applications may not always be avoidable, but it can be optimized using caching and/or a NoSQL database.

References

  • https://dzone.com/articles/caching-why-you-should-care

  • https://www.dynatrace.com/blog/understanding-application-performance-on-the-network-chattiness-application-windowing/ 

  • https://zato.io/docs/intro/esb-soa.html

application Database Relational database Cache (computing)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Top 3 Challenges Facing Engineering Leaders Today—And How to Overcome Them
  • An Introduction to Data Mesh
  • Easy Smart Contract Debugging With Truffle’s Console.log
  • Beginners’ Guide to Run a Linux Server Securely

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: