Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

What to condider for an architecture that needs to support a companies appetite for acqusition

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there
I am moving more in to architecture and the first task is to help architect a system that can scale add new companies seamlessly . Has anybody done something like that .  Can anybody refer me to any documentation about going that route
 I was considering cloud
    lift and shift , if possible
    refactor, if possible
    retire if the functionality is representative
    decommission if not applicable

 SOA ? too much work
 
 datalake   + API  {AWS/Azure ) ?


If you were going that route would you ingest those new companies offering into your product line or just integrate ?
If you integrate with new companies , you can focus on evolution . But then you have lot of tech debt from all these systems and need to maintain them
If you ingest the companies product you loose the flexibility of evolving .

Any thoughts would be appreciated
Cheers
Roger
 
Marshal
Posts: 25682
69
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, of course the answer is "It depends". First of all it depends on the company doing the acquiring, and then it depends on the companies being acquired. There's a big difference between an airline acquiring another airline and a holding company acquiring a food distribution company. And it depends on the systems that the companies being acquired already have -- you alluded to that sort of issue in your post.

I think the only thing you could do in advance is to set up a system which keeps track of the minimal amount of information you need from the acquired company, and then have the acquired company modify its system to provide that information to your system. That would be if you're acquiring a company which would continue to operate at arms length from yours -- sort of the holding company model. If you need more integration than that, it would be difficult to plan anything before knowing about the acquisition.
 
Roger Rodrigues
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Paul .
At this time the acquiring company is only focused on revenue. They want certain pieces of functionality from both companies.  They have identified some system from both the side and eventually want to integrate them with minimal effort and I do agree you design based on needs , so its hard to suggest
Cheers
Roger
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic