dmytton

11 ms·

61.
by dmytton 11y ago
Right but that only affects networking costs, because the batch is split out into individual publish API calls on Google's side, and that's what you're billed for.
62.
by dmytton 11y ago
Yes, but that has no impact on the cost. It's a flat rate in 64kb blocks. Batching and compression would only affect the networking fees from Google, not the per API call fees. If you batch up 64 1kb messages into a single batch then G
63.
by dmytton 11y ago
This is a good point, but it could be somewhat mitigated by their expected growth of up to 2M per second. To quote the full line from their blog post: > Currently our production load peaks at around 700K events per second. To account for
64.
by dmytton 11y ago
It'll be interesting to see what other numbers Spotify release in subsequent blog posts for the other services they're using. Hopefully some cost calculations can be run for those, too.
65.
by dmytton 11y ago
Batching doesn't make any difference to the pricing: > Batched calls are accounted for as multiple operations. https://cloud.google.com/pubsub/pricing
66.
How much is Spotify paying Google Cloud?(medium.com)
254 points by dmytton 11y ago|82 comments
67.
Launching an Apple TV App: What We've Learned(blog.serverdensity.com)
5 points by dmytton 11y ago|1 comments
68.
by dmytton 11y ago
Google added their 4th region - US East - in October last year[1] but it's true that this is poor effort compared to Azure and AWS. I wrote an article for InfoWorld about this at the end of last year: http://www.infoworld.co
69.
by dmytton 11y ago
I wonder if you've actually submitted a ticket to Google Cloud support at all? At the Gold level of $400/m I've had excellent experiences including: a) First responders actually being engineers who know the code well, can ref
70.
AWS vs. Google Cloud: Flexibility vs. Operational Simplicity(medium.com)
2 points by dmytton 11y ago|0 comments
71.
by dmytton 11y ago
This is S3 which isn't comparable to Google's persistent disks. S3 is equivalent to Google Cloud Storage which has "99.999999999%" durability as per https://cloud.google.com/storage/ To accurately c
72.
Automated MongoDB Backup Verification on Google Compute Engine(googlecloudplatform.blogspot.com)
2 points by dmytton 12y ago|0 comments
73.
by dmytton 12y ago
The Google Cloud status page is at https://status.cloud.google.com/
74.
Handling downtime with Yelp(plus.google.com)
1 points by dmytton 12y ago|0 comments
75.
by dmytton 12y ago
This is an interesting announcement for a few reasons: 1) It's true that VMs generally provide bad performance for high i/o applications, particularly databases. There are various ways to mitigate this such as using high IOPS driv
76.
by dmytton 12y ago
It's routing traffic to a pool of Compute Engine instances: https://developers.google.com/compute/docs/load-balancing/ht...
77.
by dmytton 12y ago
This is Google using the power of their private network. A single IP routed to your closest data center which can be done because your traffic enters their network at the closest POP and they can then route internally. Currently, you have t
78.
Automatically watering your plants with sensors, a Pi and webhooks(blog.serverdensity.com)
2 points by dmytton 13y ago|0 comments
79.
Questions ISPs must answer about Internet filtering(openrightsgroup.org)
1 points by dmytton 13y ago|0 comments
80.
How to secure your webapp(blog.serverdensity.com)
3 points by dmytton 13y ago|0 comments
81.
by dmytton 13y ago
http://dbpmail.net/essays/2013-06-29-hackers-replacement-for... is a good tutorial on replacing GMail. GMail is excellent at search and spam filtering, everything else is just a standard e-mail service. The tutorial po
82.
Improving frontend web performance using RequireJS optimiser(blog.serverdensity.com)
2 points by dmytton 13y ago|0 comments
83.
by dmytton 13y ago
A few comments on the problems: * CPU bottleneck. The mongod is no usually bound by CPU except for building indexes on existing data (which shouldn't really happen in production). The issue he's talking about is contention between the web s
84.
by dmytton 13y ago
We do this using Vagrant and Puppet and actually just blogged about it yesterday: http://blog.serverdensity.com/many-projects-with-vagrant-and...
85.
Sockii: HTTP and WebSocket aggregator(blog.serverdensity.com)
2 points by dmytton 13y ago|0 comments
86.
MongoDB write performance benchmarks(blog.serverdensity.com)
2 points by dmytton 13y ago|0 comments
87.
Growing an ops team from 1 founder(blog.serverdensity.com)
1 points by dmytton 14y ago|0 comments
88.
by dmytton 14y ago
Using the new working set analyser is going to make figuring out how much memory you need significantly easier. Giving MongoDB enough memory for your working set is the easiest way to get performance but it was quite difficult to figure it
89.
MongoDB schema design pitfalls(blog.serverdensity.com)
3 points by dmytton 14y ago|0 comments
90.
What causes delays in software projects(blog.serverdensity.com)
3 points by dmytton 14y ago|0 comments

More ›