addressalign-toparrow-leftarrow-leftarrow-right-10x10arrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1languagelaunch-new-window--smalllight-bulblightning-boltlinklocation-pinlockm-swarmSearchmailmediummessagesminusmobilemoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstar-shapestartickettrashtriangle-downtriangle-uptwitteruserwarningyahooyoutube

Re: [betaNYC] Infrastructure advice for D3/Leaflet Visualization

From: Francis G.
Sent on: Friday, January 16, 2015, 3:38 PM
I'd just use an s3 bucket. It's going to be the cheapest and most performant hosting around. If you want a CDN cloudfront (without SSL) is also dirt cheap and works great with S3.

I often use route53 for my registrar and dns and that makes it really simple to integrate. Even if you don't it's a simple as a CNAME.


-Francis

---
Francis Gulotta
[address removed]

On Fri, Jan 16, 2015 at 2:22 PM, Murray <[address removed]> wrote:
Hi All,

I am working on a visualisation that I plan to release in the next few weeks.

It utilizes D3/Leaflet based on static CSV's - the first CSV is loaded when the page loads, and is 3MB (30,000 rows) and another can be loaded if you want an extra level of detail, and is 5MB (300,000 rows).

A future version of the App might use a SQL database for JSON calls for detailed rollovers, but for now, I am only using the data in the CSV's.

I don't have that much experience with app deployment (beyond Hostmonster static HTML and Wordpress sites, or corporate n-tier apps), so I wanted to ask for some advice on the best ways to deploy this.

- Should I deploy the CSV's to a CDN, or use a cache, if so, any recommendations?
- What about serving the HTML, JS, CSS - would a host monster site be OK, or should I be looking at something like an AWS instance, Heroku, Google App Engine etc

From my point of view, I'd prefer not to have to install any software on a server - I could probably manage this, but I'd rather have a managed service that could scale if I have to.

I'm optimistically hoping for some interest generated by my visualisation, so I'd like to make sure it performs well, but I need to do this on a (personal) budget.

Any advice would be greatly appreciated!!

 
-- 
 
Murray Cox

[address removed]
www.murraycox.com






--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Murray ([address removed]) from #BetaNYC, a member of Code for America's Brigade Program.
To learn more about Murray, visit his/her member profile
To report this message or block the sender, please click here
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages

Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]

People in this
group are also in: