When the source code is not available anymore and it’s specification documents are missing, how are you going to integrate into other systems? If this isn’t complex enough, then how about smooth transition from one system to another while integration is being executed? All this while deployment should start in three weeks.
There’s nothing new in reverse engineering, but everyone who has tried it know it’s pitfalls. Successful design and execution of this kind of integration as a system to be deployed in three weeks is simply impossible.
Greitco prepared the transition, designed integration system taking into account two systems using it in parallel and deployed the solution after meticulous testing.
When instry’s leading technology company releases a new service, it’s always a big thing. Bringing products to market may not go as planned regardless of meticulous testing and planning – especially when it’s about Internet services for a userbase spanning continents and timezones.
A great many things could go wrong. Even if the solution is backed by large support organisation, unexpected problems could still arise. When the service is published likewise all of it’s possible problems are public – and these days the word spreads quickly.
When the client understood that they couldn’t solve the problem by themselves they called us. Our consults could identify the problems and apply solutions to already published service in just a few hours, this minimized the negative publicity usually arising from these kinds of problems.