B
Baqend Blog
medium.baqend.com · Company blog · on HN since 2016
The Baqend team writes technical surveys on NoSQL databases, real-time stream processing, web performance and fast website hosting.
What HN saysHN commenters cite it as a NoSQL tutorial and decision guide, and the authors argue Parse's bottleneck was usage, not the database.
20HN people shared it
5linked it in comments
22stories submitted
101story points
4 years agolast shared
2016people per year2026
Most-shared posts
- 1NoSQL Databases: A Survey and Decision Guidance8 people · 17 points · first shared 2016 · 1 comments on HN
- 2Parse Is Dead: Secrets About Their Cloud Infrastructure3 people · 6 points · first shared 2017 · discussion on HN
- 3Building a Shop with Sub-Second Page Loads: Lessons Learned3 people · 4 points · first shared 2016 · discussion on HN
- 4Rethinking Web Performance with Service Workers2 people · 2 points · first shared 2018 · discussion on HN
- 5The Core Web Vital “Largest Contentful Paint” Just Changed Dramatically1 people · 12 points · first shared 2021 · discussion on HN
- 6Real-Time Stream Processors: A Survey and Decision Guidance1 people · 10 points · first shared 2016 · discussion on HN
- 7Show HN: High Performance Website Hosting with SSL and HTTP/2 Made Simple1 people · 10 points · first shared 2017 · discussion on HN
- 8Dynamic Cache Lifetime with Immutable Cache-Control Headers1 people · 9 points · first shared 2020 · discussion on HN
- 9State of the Art in Hosting Fast Websites: Lessons Learned1 people · 9 points · first shared 2017 · discussion on HN
- 10Chrome’s Service Workers Break HTTP/2 Priorities1 people · 9 points · first shared 2018 · discussion on HN
- 11Building Static Sites in 2017: Cloud-Hosted, CMS-Backed, and API-Driven1 people · 7 points · first shared 2017 · discussion on HN
- 12Why Google’s Crux Results Are Not Reproducible with Your Real-User Monitoring1 people · 4 points · first shared 2022 · discussion on HN
- 13NoSQL Databases: A Survey and Decision Guidance (2016)1 people · 1 points · first shared 2022 · discussion on HN
- 14Bringing Web-Performance to the Next Level – An Overview of Baqend1 people · 1 points · first shared 2016 · discussion on HN
- 15Announcing availability of baqends unique client caching technology dbd9b026dc201 people · first shared 2016
What HN people wrote when they linked it
WhitneyLand · 2016-10-29
I think you are smart to consider your developer skills as a separate thing to improve. One way to objectively measure this might be to explain a technical concept to someone.
For example, could you read this article and then give an overview of the main issues of web site performance? Could you then come up with one recommendation for a performance improvement in a code base you're familiar with? Could you justify in practical terms why your recommendation was the best bang for the buck, vs. other other possible improvements?
https://medium.baqend.com/building-a-shop-with-sub-second-page-loads-l…
Now, how do you judge yourself?
1). Have the conversation with a dev whose skills and opinion you trust.
2). Record your answers on audio, and ask someone on HN to give you fair and constructive feedback. Many here would be glad to do this (feel free to ping me as well).
btown · 2017-10-16
Written format: https://medium.baqend.com/real-time-databases-explained-why-meteor-ret…
And the paper for their more scalable alternative: https://www.cl.cam.ac.uk/~mks40/pubs/vldb_2017.pdf
The devil will absolutely be in the details, but the speaker/author identifies a real pain point that bolting on a replication-log tailing system to provide realtime capabilities results in numerous write bottlenecks unless the system is architected from scratch to avoid them.
rolandm · 2017-10-08
Video from Martin Fowler about Introduction to NoSQL:
https://www.youtube.com/watch?v=qI_g07C_Q5I
Tutorial from Felix Gessert about NoSQL
https://medium.baqend.com/nosql-databases-a-survey-and-decision-guidan…
and Slides
https://www.slideshare.net/felixgessert/nosql-data-stores-in-research-…
DivineTraube · 2017-02-09
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: https://medium.baqend.com/nosql-databases-a-survey-and-decision-guidan…
erikwitt · 2016-10-24
You're right, NoSQL systems tend to be more complex and especially failure scenarios are hard to comprehend. In most cases, however, this is due to being a distributed datastore where tradeoffs, administration and failure scenarios are simply much more complex. I think some NoSQL systems do an outstanding job to hide nasty details from their users.
If you compare using a distributed database to building sharding yourself for say your MySQL backed architecture, NoSQL will most certainly be the better choice.
I'll admit though dealing with NoSQL when you come from a SQL background isn't easy. Even finding the database that fit your needs is tough. We have blog post dedicated to this challenge: https://medium.baqend.com/nosql-databases-a-survey-and-decision-guidan…