The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
How would you like to view the presentation?
Getting Started with Stratos - an Open Source Cloud Platform
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Development: A Manager's Roadmap for Success
Hi Jan,
nice presentation. However, I still don't get how CouchDB overcomes the issue with generic DB Schema. You mentioned in the minutes 11.45, that it is not good in performance, because of the JOINS. But the reason to have a generic DB Schema is because the developer want to make the application flexible. So everytime there is a new function needed, he does not need to create a new DB or a new class. Do you have answer for this?
Gruß aus Heidelberg,
Steve
Very interesting talk, is part II doing going to be posted? Jan said a lot of the answers to questions asked were in the 2nd part.
Nice presentation.
Although you are not a very good speaker.
Dragan, oh boo! I'm not a native speaker and this was a very prestigious crowd. Can you point to any specific shortcomings? :) Thanks for the feedback anyway.
@Steve, CouchDB doesn't make schema migrations go away, it just lets you do be lazy with them as you don't have to do them upfront. CouchDB views and show functions (not mentioned as they weren't invented then) can morph you docs into anything you need.
It is a trade-off question, if you can afford a 9-table JOIN and live with the performance implications, that's fine. Large websites do run without a single JOIN because they can't.
In addition, not all data is inherently relational. Being able to store things flexibly makes for more natural data handling, less code, less bugs, less headache.
Thanks for your question!
Nice presentation. Are you going to post the second part?
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
6 comments
Watch Thread Reply