It has been over a week since I visited the Qcon conference in London. It was a great experience that gave me lots of new thoughts and inspiration.
Here are my Top Quotes and Thoughts over the three days of sessions:
Stateless Architectures push the “state” problem to the database, the trend is to reclaim the state in the application server and services, and put state close to the user
To make really scalable solutions: divide, split, partition, work asynchronously, no state
Transactions are not that important
“If you can’t split it, it doesn’t scale”
Clouds and Grids are very interesting and usable today, see Amazon S3 and EC2
Java APIs are out, new (scripting, functional, non-typesafe) languages are in
There are a lot of competing shared object cache solutions out there! (Terracotta, Coherence, Cache, Gigaspaces, …)
REST is an ESB, the Web is a perfect working example of an (Enterprise) Service Bus
Continuous Performance Testing is not used by many teams
extreme: Continuous Production Deployment, some projects deploy each half hour to production (Flickr?)!
new API’s: less is better than wrong API’s
I like this phrase: “continuous health”
“the re-celabration of drag ‘n drop” (now with Ajax/Web 2.0)
you need a “compute cloud” when you get slashdotted!
“logic as a service”
the ultimate mobile app: “show me the nearby restrooms!”
first build something simple, then think of all the “…ilities”
what would (Yahoo) pipes do inside the enterprise? Think of it of a dynamic and flexible “business objects” for all the information flowing around
the concept of “openess of data”: a lot of data gets out into the open and becomes publicly owned. See the conclusion of the book: “Everything is Miscelleaneous”, businesses do not own their data anymore, only their product. Business trend is transparency.
what about privacy issues in a product such as “Google Health”?
“coupled by latency”: functionally or logically uncoupled components can still be coupled this way!
make failover part of your regular upgrades
the need for hierarchies dissappears when you make everything findable and/or taggable
If everything is findable and taggable we can get rid of the intrinsic or explicit relation ships: relationships are tags that appear by just tagging.
the accountability of software also holds for organic food: effective, reliable, reasonably priced. Compare bloathed software to industrial food: unneccessary features are like unneccessary additives.
Agile: where business meets development
scale in – scale out – scale up
what is this “Map-Reduce” I keep hearing about?
Idempotent things scale well
dynamic relocation of people at conferences due to Twitter: am I at the right track? (e.g. “This talk is great” or “Boring talk, try to leave now!”
If you tie a quote or idea to a session, I’ll tag you a star!
