DivineTraube

8 ms·

31.
Ask HN: Best Self-Hosted, Server-Side Image Optimization Tools?
59 points by DivineTraube 9y ago|37 comments
32.
Our Lessons Learned Building a Backend-as-a-Service: A Technical Deep Dive(medium.com)
7 points by DivineTraube 9y ago|0 comments
33.
A Backend for Your React and React Native Apps: Baqend React Starters(medium.com)
4 points by DivineTraube 9y ago|0 comments
34.
Building a Backend-As-a-Service: An In-Depth Survey(medium.com)
7 points by DivineTraube 9y ago|0 comments
35.
Everything We Learned Building a Backend-As-a-Service(medium.com)
6 points by DivineTraube 9y ago|0 comments
36.
How to Develop a Back End-As-a-Service from Scratch: Lessons Learned(medium.com)
7 points by DivineTraube 9y ago|0 comments
37.
How to Develop a Backend-as-a-Service from Scratch: Lessons Learned(medium.com)
8 points by DivineTraube 9y ago|1 comments
38.
Web Performance in a Nutshell: HTTP/2, CDNs and Browser Caching(medium.com)
11 points by DivineTraube 9y ago|1 comments
39.
The Lazy Man’s Guide to HTTP/2, CDNs and Browser Caching(medium.com)
12 points by DivineTraube 10y ago|0 comments
40.
CDNs, HTTP/2, TLS, Browser Caching: A Survey of Web Performance Techniques(medium.com)
9 points by DivineTraube 10y ago|1 comments
41.
Building Fast, Scalable and Secure Websites: What You Need to Know(medium.com)
9 points by DivineTraube 10y ago|0 comments
42.
State of the Art in Hosting Fast Websites: Lessons Learned(medium.baqend.com)
9 points by DivineTraube 10y ago|0 comments
43.
State of the Art in Hosting Fast Websites: Lessons Learned(medium.com)
9 points by DivineTraube 10y ago|0 comments
44.
State of the Art in Hosting Fast Websites – Lessons Learned(medium.com)
12 points by DivineTraube 10y ago|0 comments
45.
Show HN: High Performance Website Hosting with SSL and HTTP/2 Made Simple(medium.baqend.com)
10 points by DivineTraube 10y ago|0 comments
46.
by DivineTraube 10y ago
"What if you could have a fully managed database service that's consistent, scales horizontally across data centers and speaks SQL?" Looks like Google forgot to mention one central requirement: latency. This is a hosted versi
47.
by DivineTraube 10y ago
> So here are some facts and trivia that are not so well-known or published that I collected by talking to Parse engineers that now work at Facebook. As I am unsure about whether they were allowed to share this information, I will not me
48.
by DivineTraube 10y ago
I do believe you, but can your share some more hard facts? I've changed the passage to "one of the greatest". As in the disclaimer above the article, I'm mainly presenting assertions by Parse engineers, who were very sur
49.
by DivineTraube 10y ago
Sure, the benchmark and the application under test are public: http://benchmark.baqend.com/ We also do have some benchmarks comparing real-time performance, which are under submission at a scientific conference, so we canno
50.
by DivineTraube 10y ago
The Google Datastore is built on Megastore. Megastore's data model is based on entity groups, that represent fine-grained, application-defined partitions (e.g. a user's message inbox). Transactions are supported per co-located ent
51.
by DivineTraube 10y ago
Could you share what your lessons learned were? That would be a very interesting perspective. Do you disagree with some of the points?
52.
by DivineTraube 10y ago
Do you have a source for that? It is what the Parse engineers told me, but that kind of information is notoriously hard to corroborate. Any time I asked this question to MongoDB engineers they were evading concrete numbers for deployment si
53.
by DivineTraube 10y ago
Author of the post here. If you have additional key insights about the Parse infrastructure, please post them here and I will directly add them to the article.
54.
by DivineTraube 10y ago
> Some problems are caused by DBMS to backend and backend-to-frontend network utilization, which is generally not something a specialized DBMS can solve. I absolutely agree. RDBMSs are the kings of one-size-fits-most. In the NoSQL ecosys
55.
by DivineTraube 10y ago
The core problem was that the sustained number of requests did not really cause any bottlenecks. Actual problems were: - At the Parse side: expensive database queries on the shared cluster that could not be optimized since developers had no
56.
by DivineTraube 10y ago
You're right of course, I just changed that.
57.
by DivineTraube 10y ago
There are definitely some similarities. Like in Gomix, the idea of Baqend is to let developers easily build websites, bots and APIs. However, Baqend has a stronger focus on how data is stored and queried, while Gomix is more focused on a ra
58.
by DivineTraube 10y ago
The database was not the bottleneck for Parse, how they used it was. Actually that is the case for most databases systems, you have to choose a set of trade-offs your application can live with. We wrote about this in more detail here: http
59.
The AWS and MongoDB Infrastructure of Parse(medium.com)
223 points by DivineTraube 10y ago|93 comments
60.
Parse Is Dead: Secrets About Their Cloud Infrastructure(medium.com)
14 points by DivineTraube 10y ago|0 comments

More ›