Objective of OPENCAPABILITY.IN to build a catalog of capabilities which will be required to build a simple or complex application from small to large size application.
Idea of OPENCAPABILITY.IN came from challenges faced during software development when similar type of capability is needed in multiple projects from different customers. Since those project teams are completely independent and don’t even know each other, they start building piece of capability as per architecture and practices followed in the respective project. Outcome of capability is developed with very different standards, technologies, and architecture which is most likely not reusable in other projects/applications.
Secondly many organizations are moving on popular cloud platform like AWS, Azure, Google and others, same time organization have doubt about actual future of cloud platform in term of it’s shape and destination. Will be complete cloud? or hybrid? in either case I foresee a dirty price war in future among these providers. To explain this price war better let me take one example, support well reputed company XYZ is completely running it’s business on AWS which costs 500K USD per month, now what happens Microsoft approches to company XYZ and make a deal of almost 150K USD where XYZ sees a huge saving. XYZ will decide to switch to Google platform and entire IT team of XYZ will be working on AWS to GCP migration or vice-versa. Here I the role of architects who should build cloud independent solution and very few architects are following these practices.
OPENCAPABILITY.IN envisions that software developers, architecture and experts will reuse these capabilities to build a common standard application including without any cloud vendor locking if hosted on cloud.
Comments are closed