This is an interesting topic for me as well. I've got a strong SQL and database / solution design background, but have not done any web development in over 10 years. Back then it was Java on a proprietary application platform.
I'm looking at extending an identity management solution that is currently built around MS SQL Server and SSIS and potentially will use SSRS and StreamInsight as part of the solution. The solution space is Identity and Access Management, with support for Compliance and Access Intelligence being added to / extended. This is an existing framework, built to extend a specific vendor's proprietary IDM toolset, but designed to be able to integrate with other tools as well. Over time the vendor will be eliminated from the solution. Heavy use is made of views, stored procedures, triggers, dynamic SQL, against a very robust data model that so far has needed minimal change across several complex implementations. Some of the features are a data-driven policy engine (dynamic SQL allowing multiple provisioning and reporting applications to access the logic that determines who can get what, who should have what, or what can be given to users with specific demographics). a scheduling and control application, full audit / history of all actions including configuration and also user access rights, and more. The solution has to integrate into multiple corporate applications for both provisioning and access reporting purposes. It also has to be able suck data from SIEM and other tools in the future, which is a huge challenge in terms of data volumes. So, it is obvious that I don't want to go with a grounds-up redevelopment using an OO toolset, and given the environment, having everything in one cohesive application is just not going to work. The plan is to use Turbogears or other to provide web forms to configure and manage the system, as well as to create end-user facing screens to for online queries, approval / decision workbenches, access requests, compliance management and so on. This would take the form of a user workbench or portal. The overall goal is to use 'commonly available' and affordable technologies. Most clients have all the SQL Server components already, and having to add in too many additional technology components would be a negative, IMHO. For now, the options are an all-MS solution, mostly using SQL Server components (DB, ETL, complex event processing, Reporting Services, Business Intelligence) with Visual C#, Open Source with variations on the LAMP stack augmented by products like Mule, or an intelligent mix of the two. Given that I am learning the languages (C#, Python, Ruby, whatever) and the framework from the ground up, I'd be interested in opinions as to which would fit better. I doubt that the Django ORM will work. So far, SQL Alchemy seems to be the closest, the little reading I've done suggests that I could interact with the backend via standard SQK, or stored procedures / table-valued functions. While Python seems to be a fairly elegant solution, all I'm looking for is something that is quick to learn, productive to develop in, performs OK, and is robust over time (upgrades, maintenance, extension). -- View this message in context: http://old.nabble.com/Why-TG-is-a-better-option-than-RoR--tp31033408p31051883.html Sent from the Turbogears General mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
