Re: [pgbr-geral] how instagram scales

[Fabrízio de Royes Mello]

Em 14 de abril de 2012 14:38, Alexsander Rosa
escreveu:

> E quanto à escolha entre "foto no BD x foto no FS":
>
>> The photos themselves go straight to Amazon S3, which currently stores
>> several terabytes of photo data for us. We use Amazon CloudFront as our
>> CDN, which helps with image load times from users around the world (like in
>> Japan, our second most-popular country).
>
>
>
Como consta nessa observação eles utilizaram o serviço de distribuição de
conteúdo da amazon, o "Amazon CloudFront", o que significa que eles não
estão armazenando esses "terabytes de fotos" no PostgreSQL... a não ser que
o Amazon faça algo nesse sentido, mas creio que não seja esse o caso.

Há algum tempo postei uma palestra do Diogo [1] sobre esse assunto e alguns
pontos a considerar sobre o uso de BLOBs.

[1] http://www.slideshare.net/diogobiazus/arquivos-no-banco

-- 
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
___
pgbr-geral mailing list
pgbr-geral@listas.postgresql.org.br
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral

Re: [pgbr-geral] how instagram scales

[Alexsander Rosa]

E quanto à escolha entre "foto no BD x foto no FS":

> The photos themselves go straight to Amazon S3, which currently stores
> several terabytes of photo data for us. We use Amazon CloudFront as our
> CDN, which helps with image load times from users around the world (like in
> Japan, our second most-popular country).


Em 14 de abril de 2012 14:29, Fábio Telles Rodriguez  escreveu:

> Olhem que interessante...
>
>
> destaques:
>
>- Fabric  is used
>to execute commands in parallel on all machines. A deploy takes only
>seconds.
>- PostgreSQL (users, photo metadata, tags, etc) runs on 12 Quadruple
>Extra-Large memory instances.
>- Twelve PostgreSQL replicas run in a different availability zone.
>- PostgreSQL instances run in a master-replica setup using Streaming
>Replication . EBS is used
>for snapshotting, to take frequent backups.
>- XFS as the file system. Used to get consistent snapshots by freezing
>and unfreezing the RAID arrays when snapshotting.
>- Pgbouncer  is used pool
>connections  to PostgreSQL.
>
>
>
>
> http://highscalability.com/blog/2012/4/9/the-instagram-architecture-facebook-bought-for-a-cool-billio.html
>
>
> --
> Atenciosamente,
> Fábio Telles Rodriguez
> blog: http://www.midstorm.org/~telles/
> e-mail / gtalk / MSN: fabio.tel...@gmail.com
> Skype: fabio_telles
>
>
> ___
> pgbr-geral mailing list
> pgbr-geral@listas.postgresql.org.br
> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
>
>


-- 
Atenciosamente,
Alexsander da Rosa
http://rednaxel.com
___
pgbr-geral mailing list
pgbr-geral@listas.postgresql.org.br
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral

[pgbr-geral] how instagram scales

[Fábio Telles Rodriguez]

Olhem que interessante...


destaques:

   - Fabric  is used to
   execute commands in parallel on all machines. A deploy takes only seconds.
   - PostgreSQL (users, photo metadata, tags, etc) runs on 12 Quadruple
   Extra-Large memory instances.
   - Twelve PostgreSQL replicas run in a different availability zone.
   - PostgreSQL instances run in a master-replica setup using Streaming
   Replication . EBS is used for
   snapshotting, to take frequent backups.
   - XFS as the file system. Used to get consistent snapshots by freezing
   and unfreezing the RAID arrays when snapshotting.
   - Pgbouncer  is used pool
   connections  to PostgreSQL.



http://highscalability.com/blog/2012/4/9/the-instagram-architecture-facebook-bought-for-a-cool-billio.html


-- 
Atenciosamente,
Fábio Telles Rodriguez
blog: http://www.midstorm.org/~telles/
e-mail / gtalk / MSN: fabio.tel...@gmail.com
Skype: fabio_telles
___
pgbr-geral mailing list
pgbr-geral@listas.postgresql.org.br
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral