It does'nt really make any sense for enterprise's / ISV's developers to write all the SaaS-ification components all by themselves! SaaSifying an app is a huge task and requires lot of thinking and re-thinking, since now the app needs to cater to the cloud aspects of programming.
A few main questions a re-engineering team needs to answer are
A few main questions a re-engineering team needs to answer are
- What level of Multi-tenancy a SaaSified app need to be at to maximize the benefits of cloud?
- What to do to minimize cloud PaaS vendor lock-in?
- What instrumentation and management components need to be written? Can somebody else help?
- How to make a SaaS app extensible, flexible, auto-scalable(more on this later?), resilient(this too bit later?)...?
- Which parts of the application could be outsourced? Can they really be outsourced without leaking my precious concept? Does this too require any architecture consideration?
- What are other such big ticket questions?
You got that right this time! There are so many such questions which all need to get answered for this humongous task!
Scared? No use... lets find way(s) tackle these one by one!
[If you too are the one who thinks "what the hell is this blog talking here!?!", please have patience for a bit. Promise, it will all make sense in a few posts... Hope "Re-Engineering" is really one of your concerns and you work closely with at-least one such team, otherwise it might never make sense!]
No comments:
Post a Comment