AroundAround
Sign in Sign up
Menu

Estimation of a project to migrate to Spring Boot

Emma Brown
admin
#spring-boot # #estimation-technique
Share post:
Share

How to estimate the effort for converting an existing technology to Spring Boot? The process involves evaluating the current system, defining the scope of the migration, assessing required skills, and breaking down tasks into manageable components.

How can an estimation be reached for a project that involves converting a specific technology to Spring Boot?

Solution in a Nutshell

  • Analyse each microservices and understand what are the components or technology being used; following components checked
    • Protocol List of values REST, SOAP, Event 20%
    • Number of endpoints if REST
    • Number of external integrations 30%
    • Data base used or not, data base name 20%
    • Messaging systems, SQS etc 15%
    • Fiels torages used S3, Sharepoint etc
    • business rules complexity 15%
  • Once we identified above component, we put waightage as above for each components total should be 100%
  • then we will put the score calculation agains t each microservices eg if(database yes) then 1*15%, total score will be round to whole number
  • after this the score , the API will be put into seperate buckets like XS, S, M, L and XL tshirt sizes
  • the buckets agin catgeorize like XS, S is simple , M is mediumand L and XL is Complex it will get in th 20%, 60%, 20% ratio in most of the cases
  • then we will put the number of days required for overal migration and tht will be in PD (mandays) for a single person
  • again we can make it to 5 person teams with dev, testers ux etc and see number of months required
  • this further can stream line by making number of teams and can target to complete by 6-10 months
  • this will share with the client and get approval
  • during presentation highligth things likehow many SOAP services. REST Services, what are the AWs services used how many integrations etc as insights