Our Work

Automotive company usage of microservices and Elastic Search for their catalogue & Order systems.


Our Client an NA Automotive company is generating huge terabytes  of  transactions data for their catalogue & orders system which need to be searched in matter of few milliseconds and also they needs a system which is 100% fault tolerant  to  KTree used Elasticsearch and AWS SQS to deliver this system and also to make it microservices enabled.

Industry : Automobiles
Country : USA
Auto Part Distributors
  • Businesss Requirements and Challenges.

    • Server-less architecture, 100% High-Availability, Zero fault tolerance and continuous monitoring were four main components of this project and KTree implemented this using AWS Lambda, Amazon SQS Queue, Amazon Elastic, CloudWatch Rules  and CloudWatch Dashboards.
    • These transactions has huge financial impact, and it requires lot of check and pre checks so each Single transaction is accounted for.

    • The complex logical layer and the interactions between the website and third party integration's are written in PHP and Python code.
    • Another major requirement was to have near real-time data analysis for their hourly transactional data, and also data which is searchable and can be statistically represented in graphs & Charts. Traditional BI systems typically falter at this near real-time data.
    • System need to ingest terabytes of data from multiple servers and this ingest happens 24/7 and 365 days which requires 100% high-availability.

    • The architecture has been built with integration of the components and frameworks like OpenERP, Yii, Postgress, Postfix, Pentaho.
  • Challenges & Requirements:

    • Orders history data, sales summary, parts search summary &  Integration & authentication details were few indices which were getting updated regularly.
    • Data shippers process data from sqs queue to ElasticSearch and this need 100% high availability too.
    • Data Security & implementing best practices for protecting the endpoints traffic from only VPC/VPN or known applications/domains. 

    • Need Content
    • Need Content
    • Need Content
    • Need Content
    • Need Content
  • Architecture Overview

    • AWS cloud services used and the architecture overview Diagram (Right Side)
      CloudWatch Rules    
      Simple Service Queue (SQS)
      Lambda Service
      ElasticSearch Service.
      CloudWatch Metrics
    • By using SQS we have decoupled our standard Java application components successfully, and made our overall architecture of our as microservices enabled.
    • Using SQS and lambda helped the client in scaling transparently based on the demand.

    • Role based access to the resource data.
    • SAAS based platform to access the instance by users.
    • Supports around 16 languages
    • Export and import options
    • Drag and Drop project based on status 

The Benefits

    • Moving to AWS has also made our client's IT department less reliant on IT support resources and client reported this has given them  overall cost benefit of about 20-30%.
    • Since migrating to AWS, Our client has seen measurable improvements in the bottom line, as 10 million+ of transactions are pushed to different elastic indices in multi-threaded distributed architecture with minimal or zero fault tolerance.
    • Usage of cloudwatch metrics & Alerts has helped us to respond in advance and do the maintenance activities for 100% HA.
    • With the usage of AWS SQS, we made the architecture microservices enabled and less coupling, and the development teams started adding features more quicker than before.
    • Data shippers were implemented in AWS lambda (serverless architecture) which does not need any hardware setup or maintenance or downtime. These lambda functions read SQS queue and ingest data directly to elasticsearch service indices. Multiple Lambda functions for the same queue in the peak time were created easily which helped reduced the ingestion time.

Free Software Consultation with our Experts!

No Obligation!

Read More

Read more about KTree

KTree, a Global IT Company

What and how the processes are structured in KTree?

KTree follows CMMi process to T. Defined and Mature processes for Coding, Code Reviewing Exercises, QA Process with focus on Performance testing & Load Testing

Where is KTree's Web and Mobile application Development done?

Most of our Development is done from our Hyderabad Development Center. Hyderabad is known for its rich heritage and exotic food apart from abundant IT Talent.

How KTree makes outsourcing project a positive experience?

True collaboration, transparent and constant communication, visibility and traceability are the key for success. The other major one being requirements engineering.

What is Success mantra of KTree, as one of the respected web development company?

Agile Methodology + Strong Documentation + Powerful Web & Mobile Frameworks + Solid KTree Team = Great Web & Mobile Applications within time.

Any other Differentiation which KTree has, which it can offer?

Having worked on hundreds of Web & Mobile Application projects, KTree teams tremendous knowledge & expertise gives very good head-start for projects which helps clients save many man-months

What Development methodology KTree follows and why?

KTree development team follows Agile methodology because of its suitability to web and mobile application development. Scrum helps improve Agility due to its simplicity and flexibility

Our Clients