Difference between revisions of "Poppy/Server Architecture"
< Poppy
Amit Gandhi (talk | contribs) (Created page with "Poppy provides a driver based architecture, allowing for different types of transports, data stores, and CDN providers. Poppy (by default) ships with a CassandraDB Data Store...") |
Amit Gandhi (talk | contribs) |
||
| Line 5: | Line 5: | ||
''The team recommends using CassandraDB in a production environment to allow for easy geo-replication of configuration data. This allows operators to publish a single global endpoint. utilizing geo-dns, and distribute Poppy servers all around the world, while having their data geo-replicate to all of their servers.'' | ''The team recommends using CassandraDB in a production environment to allow for easy geo-replication of configuration data. This allows operators to publish a single global endpoint. utilizing geo-dns, and distribute Poppy servers all around the world, while having their data geo-replicate to all of their servers.'' | ||
| − | + | [[File:PoppyArchitecture.png|center|Server Architecture (Poppy)]] | |
| − | [[File: | ||
Revision as of 21:37, 5 August 2014
Poppy provides a driver based architecture, allowing for different types of transports, data stores, and CDN providers.
Poppy (by default) ships with a CassandraDB Data Store, and a Pecan based WSGI Transport. The team plans to add a SQLAlchemy compatible Data Store in the near future.
The team recommends using CassandraDB in a production environment to allow for easy geo-replication of configuration data. This allows operators to publish a single global endpoint. utilizing geo-dns, and distribute Poppy servers all around the world, while having their data geo-replicate to all of their servers.
