(English) A simple SimpleDB use case
Monday, May 4th, 2009Ci spiace, ma questo articolo è disponibile soltanto in English.
Ci spiace, ma questo articolo è disponibile soltanto in English.
Ci spiace, ma questo articolo è disponibile soltanto in English.
Ci spiace, ma questo articolo è disponibile soltanto in English.
Ci spiace, ma questo articolo è disponibile soltanto in English.
Ci spiace, ma questo articolo è disponibile soltanto in English.
Da oggi il mio blog supporta più di una lingua, per la precisione l’Inglese e l’Italiano.
Il punto è che mi sono sentito un po’ a disagio scrivendo solo in Inglese alcuni articoli che vorrei fossero letti anche nella mia lingua, per supportare la diffusione delle tecnologie e delle idee che ritengo importanti anche nel Paese in cui vivo e lavoro.
La scelta della lingua avviene selezionandola nella home page in alto a destra. Ho aggiunto il supporto multilingua a Wordpress installando il plugin qTranslate, molto ben fatto anche se con qualche piccolo difetto.
Buona lettura!
Some weeks ago one of my customers decided that one of its biggest ASP.NET web intranet projects needed a sort of architectural revision, mainly to support better its customers with built-in fault tolerance but also to unchain development of the various sub-projects through better separation between software modules.
When small software companies get bigger they embark on what can be a bumpy ride of change. One of those changes will probably be to do with the way they tackle the analysis phase of the software development life-cycle (SDL). Just to be clear, when I say “analysis phase”, I mean the part before coding starts i.e. requirements elicitation, analysis and system specification.
Typically (although I am sure that there are plenty of shining examples where this is not the case) small software companies with a handful of developers, where the entire SDL for a project is covered by one or two developers, tend not to have a formalised analysis phase. Why is that?
As expected, at least by me, Amazon EC2 is evolving in a more “concrete” platform good for web hosting; in fact, some time ago I received a mail from AWS announcing two new features: Elastic IP Addresses and Availability Zones (you read for sure the news also on Slashdot: Amazon EC2 Now More Ready for Application Hosting, isn’t it?)
Only a small note to let you know that Amazon is hearing us and added a new feature to EC2: persistent storage.
As a subscriber of AWS services yesterday I received an email in which Amazon announces that we “will be able to create volumes ranging in size from 1 GB to 1 TB, and will be able to attach multiple volumes to a single instance. Volumes are designed for high throughput, low latency access from Amazon EC2, and can be attached to any running EC2 instance where they will show up as a device inside of the instance…“.
The mail ends saying that the new functionality “will be publicly available later this year” and offers a link to request to join the private beta program; I subscribed it and will let you now as soon as I’ll put my hands on it.