non è che sia un esempio particolarmente eclatante o importante, ma...
... ascoltate qui la storia di questo presunto attacco di squalo. (gli squali sono animali che amo, la mia prima - ed unica - società si chiamava proprio shark). La musica di Spielberg, le immagini, il pugno sul muso per liberarsi.
Poi googlate un po' e troverete che il tipo è stato già arrestato, e che probabilmente si è ferito con una finestra in un tentativo di furto.
Quando spariranno definitivamente i giornali? Anche i pochi decentemente online mantengono evidentemente i difetti del cartaceo: due anni? cinque? dieci?
giovedì 20 dicembre 2007
giovedì 13 dicembre 2007
Great fun @ Javapolis…
Ok, it was a BOF, and at 9.00 PM. And, we didn't manage to get the Javapolis tickets in time (ironically, I am also a Jug Leader with a free pass), so we were in the unfortunate position of being speakers withouth the rights to stay at the conference :(
But the talk has been great fun, lot of questions and interaction. Being the last BOF we also used an extra half-hour... and we had the terracotta guys attending the meeting (isn't it strange to hear other people talking about your product? That probably means your baby is moving up in the world), they also helped us on some questions, mostly details on an undocumented feature like the active/active server master Ari mentioned in its response to Bela Ban
Definitely, terracotta is a great product with a very competent team. And me and Sergio had great fun in hacking Jira. Next target: cluster Confluence?
But the talk has been great fun, lot of questions and interaction. Being the last BOF we also used an extra half-hour... and we had the terracotta guys attending the meeting (isn't it strange to hear other people talking about your product? That probably means your baby is moving up in the world), they also helped us on some questions, mostly details on an undocumented feature like the active/active server master Ari mentioned in its response to Bela Ban
Definitely, terracotta is a great product with a very competent team. And me and Sergio had great fun in hacking Jira. Next target: cluster Confluence?
giovedì 6 dicembre 2007
Scarlet news…
Sergio beat me on time and announced Scarlet beta 2
Well, at least this delay gives me more time to comment on some blog reactions from Terracotta friends Orion and Ari :)
As Ari said, clustering with an invasive situation is really a different beast. I'd add that it could be literally devastating for your legacy project. Atlassian Confluence is a real world example, it has been a 54 man/month effort according to an atlassian presentation given some months ago. Clustering Jira with Terracotta has been much easier than that, and assuming that confluence and jira have the same complexity (which is a reasonable assumption, coming from the same company and sharing a similar architecture), we can safely say that the effort to cluster with TC has been a tiny fraction than 54 man/month, so much much better than that.
Regarding the transparent clustering claim, well... for us it's been more a translucid one ;) Dealing with legacy J2ee code can be very tricky, and using a straightforward terracotta solution (ie simply putting the objects in your shared roots and writing some XML) is not always feasible/performant/possible. We described some of the issues we found in our talk at javaday (which should be replicated at next javapolis, if we can find the air tickets :) ).
For example, dealing with a lot of uncorrectly synchronized home-grown caches forced us to write a common cache adapter on top of them, using a lock-striping solution and than TC-ize that.
Not exactly the kind of stuff you code in the weekend!
Well, at least this delay gives me more time to comment on some blog reactions from Terracotta friends Orion and Ari :)
As Ari said, clustering with an invasive situation is really a different beast. I'd add that it could be literally devastating for your legacy project. Atlassian Confluence is a real world example, it has been a 54 man/month effort according to an atlassian presentation given some months ago. Clustering Jira with Terracotta has been much easier than that, and assuming that confluence and jira have the same complexity (which is a reasonable assumption, coming from the same company and sharing a similar architecture), we can safely say that the effort to cluster with TC has been a tiny fraction than 54 man/month, so much much better than that.
Regarding the transparent clustering claim, well... for us it's been more a translucid one ;) Dealing with legacy J2ee code can be very tricky, and using a straightforward terracotta solution (ie simply putting the objects in your shared roots and writing some XML) is not always feasible/performant/possible. We described some of the issues we found in our talk at javaday (which should be replicated at next javapolis, if we can find the air tickets :) ).
For example, dealing with a lot of uncorrectly synchronized home-grown caches forced us to write a common cache adapter on top of them, using a lock-striping solution and than TC-ize that.
Not exactly the kind of stuff you code in the weekend!
Iscriviti a:
Post (Atom)