ovaistariq

9 ms·

91.
by ovaistariq 4y ago
HTTP/2—the successor of the HTTP protocol—provides advantages over its predecessor, such as multiplexing and server push. Although it's a significant improvement over HTTP/1, HTTP/2 is it a replacement for WebSockets? In
92.
by ovaistariq 4y ago
I hope you are sold now :) I don't really have experience pitching our own product. So the feedback on HN has been enlightening.
93.
by ovaistariq 4y ago
The limitations are listed here: https://docs.tigrisdata.com/apidocs/#section/Limitations Apart from the size of the document, there is no limit on the size of the array or the depth of nested data. We plan on sub
94.
by ovaistariq 4y ago
Avoiding rebuilding the table is definitely possible for certain schema changes like adding a new field. But supporting data type changes without rebuilding is not ideal. It will lead to data quality issues and complexity on the application
95.
by ovaistariq 4y ago
Schema migrations are supported but there are some restrictions. Here are some docs, we will be adding more details: https://docs.tigrisdata.com/overview/datamodel Assuming you have declared your schema as shown here
96.
by ovaistariq 4y ago
It has significant usage across large companies such as Apple, Snowflake, Epic Games, VMWare, etc. I don't see it going closed source. Besides that, here Tigris is taking the responsibility for the product as it is abstracting Foundati
97.
by ovaistariq 4y ago
We love FDB for all the reasons you mentioned and decided to build on top of it. It is quite flexible and provides a low enough primitive to be used as a building block for systems like Tigris. However, if you are an application developer l
98.
Skipping the boring parts of building a database using FoundationDB(blog.tigrisdata.com)
75 points by ovaistariq 4y ago|41 comments
99.
by ovaistariq 4y ago
Building distributed database systems correctly from the ground up is a notoriously hard problem. We have seen this firsthand building Docstore at Uber. This is one of the most confusing aspects of the modern data infrastructure industry, w
100.
by ovaistariq 4y ago
I agree details are important as well. Do you think this is providing enough information: https://docs.tigrisdata.com/overview/architecture ? Or would you suggest adding more technical details? There are essentially 3
101.
by ovaistariq 4y ago
I think that's how most people interested in solving problems would look at it the way you have described - 'does it solve/help with problem X I already know' or 'what is this for and why does it matter'. And w
102.
by ovaistariq 4y ago
Again, I really appreciate the feedback. So regarding the video, if I understand correctly your suggestion is that use-case driven videos would be better? You make a great point regarding the tutorial. Where would you want to see it? In tut
103.
by ovaistariq 4y ago
Take a look at the high level architecture here: https://docs.tigrisdata.com/overview/architecture . I will be happy to go into more details. `docker run -d -p 8081:8081 tigrisdata/tigris-local:latest` essentially
104.
by ovaistariq 4y ago
We have prepared this use-case video to depict how Tigris can be used: https://youtu.be/G489hasvgio
105.
by ovaistariq 4y ago
Great feedback. We do want to speak to folks building new applications as Tigris takes away the infrastructure burden completely from the start. We want to bring the same API experience to "data" as you get when using Stripe API f
106.
by ovaistariq 4y ago
Does this explain it in a better way: https://docs.tigrisdata.com/overview/features
107.
by ovaistariq 4y ago
People can try it out in local development environment: https://docs.tigrisdata.com/quickstart Besides that, it is Apache2 license which means folks can deploy it to their k8s and run it.
108.
by ovaistariq 4y ago
Thanks for the feedback on the doc. At the core of it, it is a transactional document database that uses FoundationDB under the hood for data persistence. It automatically provides search capability on the data stored (similar to Elasticsea
109.
by ovaistariq 4y ago
The REST+json part is one part of it. FoundationDB is an awesome tech and proven at scale. But it only provides a simple key-value interface. But we have built multiple features on top of it to enable it to be used as complete platform. Que
110.
by ovaistariq 4y ago
We use FoundationDB’s transactional key-value interface as the underlying storage engine. This provides us with a low level building block that can scale to peta bytes of data. The reason it is more than a database is because it provides mo
111.
Show HN: Tigris – open-source developer data platform for your next app(docs.tigrisdata.com)
58 points by ovaistariq 4y ago|24 comments
112.
by ovaistariq 4y ago
Referencing the text from documentation: “ StoneDB is optimized for OLAP applications. StoneDB that runs on a common server can process complex queries on tens of billions of data records, while ensuring high performance. Compared to datab
113.
Why do companies need so many different database technologies?(blog.tigrisdata.com)
10 points by ovaistariq 4y ago|0 comments
114.
by ovaistariq 4y ago
This is a great read, thanks for sharing the architecture. I am glad to see the increase in adoption of FoundationDB. It is a great piece of technology why is also why we are using it as a core component for Tigris https://docs.t
115.
by ovaistariq 5y ago
There is more to a database than a raft implementation. A raft implementation would provide data replication between members and leader election. That is just one piece in a distributed database architecture. You then need a storage engine
116.
by ovaistariq 5y ago
I think of FoundationDB as a low level persistence layer that you can use to build a fully functional database on top with more complex querying capability. It provides the core set of semantics such as data replication, globally ordered tr
117.
Docstore – Uber's scalable operational database(eng.uber.com)
2 points by ovaistariq 5y ago|0 comments
118.
Better MySQL Metrics in Datadog(community.lithium.com)
4 points by ovaistariq 12y ago|0 comments
119.
by ovaistariq 13y ago
Wahoo!! Congratulations Percona.
120.
Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact(ovaistariq.net)
1 points by ovaistariq 15y ago|0 comments

More ›