Skip to main content

Key to adopt open source product

Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache.
Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation.

1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software.
2. I would avoid involving external consultants for 2 reasons.
     a. I am not sure, they would bring necessary expertise on to table
     b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all)
3. Alternative to that is to build the team that is capable of debugging - This is very important, In my opinion its the key.
4. Use intelligent guess - like how do you implement given the scenario, this would take to find the problem
5. Also, I would advise to keep any customization minimum, keep the dependency on open source product to minimum, not that I dont like them, but it gives me the flexibility to adopt to new solution, when it arrives
6. If there is large chunk of functionality needed, then I would propose build it as an external module and integrate with open source product, rather than extending it.
7. Last but not least, not all requirements are the candidates for customization or development. This is where business analysis comes into picture. We need to model the business requirement in different or novel way understanding the constraints of the product in focus. This is another key to success.

The most annoying issue in open source implementation is not fixing, but in finding it. The community forums do their bit, but in case of Kaltura, hardly there is involvement from experts. Will keep updating ...
Take care.



Comments

  1. Twinkle ComputersFebruary 9, 2013 at 9:59 AM

    Nice blog RP. Please keep updating it.

    As you know, we faced one major issue with kdp skin yesterday and because of it the player was not loading. We suspected the issue with cloud front url, but it actually got resolved when we reverted the skin file to the original one.

    Not sure exactly the reason but suspecting it could be file corruption issue, but it took lot of time and team effort to find and fix it.

    You helped us at the right time when we lost hope on the player.

    Thanks
    Shylesh

    ReplyDelete

Post a Comment

Thanks for your comments.

Popular posts from this blog

Secure your application on cloud

Handling sensitive data Define sensitive data for your application. Classify as sensitive data and confidential data. Sensitive data is something like password, credit card account number, something that you should not compromise at all. Confidential data could be your customer’s health record, something that requires your permission before its usage. So, you need to define sensitive data in the context of your application. There are many ways to protect the sensitive data in transit; the easiest way is to use SSL. This is nothing different than handling sensitive data in any traditional application.   However, make sure you apply this rule while designing your application for cloud deployment. Alternatively, you can encrypt the sensitive data and transport. Be noted that any kind of protection you design, will have implications on performance. However this is ignorable considering the nature of sensitive data. If you just want to protect your data from being tampered du...
Post a Comment
Read more

Object orientation and Service orientation

Object orientation is all about modeling the real world information mainly through encapsulation, abstraction, polymorphism, containment, inheritance and so on. In simple words, an object contains the data structures and methods to change the content state. A typical OO run-time manages the life cycle of objects. You can create as many objects as required as long as the run-time does not over run its memory. Service orientation requires you to encapsulate a process. The operations of a services are interaction points with the particular process. Data structures are the arguments for these operations. Service run-time shall validate the correctness of the process. Service can have multiple invocation instances, not multiple instances of service itself. Example: TrainTicketBookingService involves a process. - Check the train timings //  interaction point - Check the seat availability // interaction point - Issue ticket // interaction point There could be many ticket...
Post a Comment
Read more