In the open source each software is developed independently by the same or different vendor/enthusiast. Some of the software uses other software as base with each software may or may not be aware others are using it and each software not guranteeing release assurance, we now have a unique problem which does not exist in Microsoft World.
Lets say we have 3 Software Manufacturers M1, M2 and M3
They produce the following software and its corresponding versions
M1 - Software 1 (S1) current Version V4
M2 - Software 2 (S2) current Version V5 uses M1 S1 V3
M3 - Software 3 (S3) current Version V3 uses M1 SI V2 and M2 S2 V3
We now have manufacturer M2 trying to use the software of M1 S1 V3 and build on top of it. So the M3 S2 V5 is currently using M1 S1 V3.
The M1 may or may not be aware that M 2 is using the software. Now M1 decides that he needs to be bleeding edge in software development and comes up with Version 4 of S1. He now puts a notice saying that these are the things that would break or says that previous versions won't be supported further.
M2 has two problems one, when ever M1 changes S1 he needs to stop what ever he is doing and make sure that M2 software S2 works with S1. He also has to take care of his feature sets that is built on top.
The similar is the case when other manufacturers uses different software and its corresponding version. In this case M3 S3 depends on both M1 S1 and M2 S2.
So how do you now pick a technology if each version is not compatible.
Choice 1
Run each instance ecosystem separately for their usecases when collaborating with different software. Namely in order to get the best of the software and then keep replicating the data between the different ecosystems.
eco system 1 M1 S1 V4
eco system 2 M2 S2 V5 with another instance of M1 S1 V3
eco system 3 M3 S3 V3 with another instance of M1 SI V2 and M2 S2 V3
Choice 2
Run the LCM version of all the dependent software are wait for the software manufactures to certify for compatibility and learn to live with the delay in bleeding edge.
eco system 1 downgrade to M1 SI V2 as this is the lowest dependency by M3
eco system 2 downgrade to M2 S2 V3 with the same instance of M1 SI V2
eco system 3 M3 S3 V3 with the same instance of M1 SI V2 and M2 S2 V3
in summary there is only one instance of M1 SI V2, M2 S2 V3 and M3 S3 V3
Choice 3
A combination of Choice 1 and Choice 2
Lets say we have 3 Software Manufacturers M1, M2 and M3
They produce the following software and its corresponding versions
M1 - Software 1 (S1) current Version V4
M2 - Software 2 (S2) current Version V5 uses M1 S1 V3
M3 - Software 3 (S3) current Version V3 uses M1 SI V2 and M2 S2 V3
We now have manufacturer M2 trying to use the software of M1 S1 V3 and build on top of it. So the M3 S2 V5 is currently using M1 S1 V3.
The M1 may or may not be aware that M 2 is using the software. Now M1 decides that he needs to be bleeding edge in software development and comes up with Version 4 of S1. He now puts a notice saying that these are the things that would break or says that previous versions won't be supported further.
M2 has two problems one, when ever M1 changes S1 he needs to stop what ever he is doing and make sure that M2 software S2 works with S1. He also has to take care of his feature sets that is built on top.
The similar is the case when other manufacturers uses different software and its corresponding version. In this case M3 S3 depends on both M1 S1 and M2 S2.
So how do you now pick a technology if each version is not compatible.
Choice 1
Run each instance ecosystem separately for their usecases when collaborating with different software. Namely in order to get the best of the software and then keep replicating the data between the different ecosystems.
eco system 1 M1 S1 V4
eco system 2 M2 S2 V5 with another instance of M1 S1 V3
eco system 3 M3 S3 V3 with another instance of M1 SI V2 and M2 S2 V3
Choice 2
Run the LCM version of all the dependent software are wait for the software manufactures to certify for compatibility and learn to live with the delay in bleeding edge.
eco system 1 downgrade to M1 SI V2 as this is the lowest dependency by M3
eco system 2 downgrade to M2 S2 V3 with the same instance of M1 SI V2
eco system 3 M3 S3 V3 with the same instance of M1 SI V2 and M2 S2 V3
in summary there is only one instance of M1 SI V2, M2 S2 V3 and M3 S3 V3
Choice 3
A combination of Choice 1 and Choice 2
No comments:
Post a Comment