slisznia

3 ms·

1. 1.▲
   by slisznia 7y ago

   The volume and storage numbers you quoted call for breaking up a monolithic system. We have a similar overall volume of transactions and storage needs to yours but we reside in all US regions, tens of AZs. If one AZ went down, a small fract
2. 2.▲
   Splitting large MySQL DB into smaller ones(dba.stackexchange.com)

   1 points by slisznia 8y ago|0 comments
3. 3.▲
   Is RDF/Dgraph suitable for financial data?

   1 points by slisznia 8y ago|1 comments
4. 4.▲
   Google Instant Apps remind me of “ActiveX” era

   1 points by slisznia 10y ago|0 comments
5. 5.▲
   by slisznia 10y ago

   Few more tests of the same aggregate reports to gain better perspective. MySQL 5.6.27 was the clear winner. RDS MySQL 5.6.27 T2 Large: 0m34.977s RDS MariaDB 10.1.14 T2 Large: 0m38.097s RDS MySQL 5.7.11 T2 Large: 0m40.408s
6. 6.▲
   Surprised to see AWS Aurora *slower* than RDS

   7 points by slisznia 10y ago|3 comments
7. 7.▲
   (Interview) Pixel-Perfect Images For Every Screen(superbcrew.com)

   1 points by slisznia 13y ago|0 comments
8. 8.▲
   by slisznia 13y ago

   Confirmed. With few exceptions like 9-Patch or SVG, ImageMagick is our workhorse.
9. 9.▲
   (Chicago startup) puts "Photoshop" behind CDN(redid.net)

   3 points by slisznia 13y ago|2 comments