Compose Articles

They're the best we've found as well, but there are lots of managed database providers of all kinds. https://www.compose.com is another big one.

When I last looked, https://www.compose.com/ did 'blind hiring' - they judge you by a small, representative work task rather than the credentials you boast. OK, you'll spend quite some time if you want to nail it. But hey. Edit: I got quite far in their little puzzle-box of a recruitment process, but didn't quite make it.

I really wish this were priced more along the lines of https://www.compose.com/pricing - a $200/m floor is a tough dB cost to absorb on smaller yet important projects. Suppose an app has a few mb of data and maybe one day hits 100mb of awesomeness I really have to pay $200/m here? I get it, I love Aws, just wish this was priced differently.

Even IBM Cloud is largely built from SoftLayer, Cloudant, Compose, Cleversafe etc, RedHat fits perflectly with IBMs strategy since 2014. Interestingly enough, IBM has even left https://www.compose.com/ as a standalone entity for now.

Hi, author here :) I've written a few similar posts and would love to get feedback from HN. Using PostgreSQL through SQLAlchemy[0] Flask vs Django[1] [0] https://www.compose.com/articles/using-postgresql-through-sqlalchemy/ [1] https://www.codementor.io/garethdwyer/flask-vs-django-why-flask-might-…

> During the work day, you'd join is in Slack for 8 hours. That's amazing! For everybody else that shares my amazement, I found https://www.compose.com/articles/how-compose-uses-interviewed-com-and-… that touches on said hiring practice, but I'd love to hear more.

The only names I recognized on there was Influx and Compose. Influx actually looks like they use AWS for their cloud offering now: https://www.influxdata.com/announcing-influxcloud-fully-managed-influx… and Compose deploys to AWS, Google, Softlayer and only to D.O for MongoDB classic whatever that is: https://www.compose.com/mongodb

Check this: https://www.compose.com/

Unless there is a good reason, I think in that situation I would probably try to avoid storing those tens of millions of small json files directly on the filesystem. For example : have you considered storing that data in jsonb/postgresql https://www.compose.com/articles/faster-operations-with-the-jsonb-data… ? (or even just in an sqlite db https://www.sqlite.org/fasterthanfs.html )

Terrible consistency model. Judging a consistency model as "terrible" implies that it does not fit any use case and therefore is objectively bad. On the contrary, there are plenty of use cases where "eventually consistent writes" is the perfect use case. To judge this as true, you only have to look and see that every major database server offers this as an option - just one example: https://www.compose.com/articles/postgresql-and-per-connection-write-c…

Thanks for the link to Pgbouncer, I'll check that. I'm using Cloudflare Workers which are distributed on the CF network and run at the edge to reduce latency. Achieving the same thing with containers would be probably complicated and expensive. Right now I'm using Fauna DB which is also distributed and doesn't have connection limits, but I want to explore all my options. Edit: If anyone wants to know more about PGBouncer and pooling with postgres I found this article very informative: https://www.compose.com/articles/how-to-pool-postgresql-connections-wi…

They don't even do multi-node for node sizes smaller than 58gb RAM. Dedicated master is not available until the cluster size at least 6 nodes of 58gb RAM. Multi-master is not available. I'm not sure if this is based on research or optimal configuration size, but it seems very expensive to get a 3-node cluster going on ElasticCo. Does anybody have experience with compose? (https://compose.com/databases/elasticsearch)

https://www.compose.com/articles/getting-started-with-elasticsearch-an… https://blog.raananweber.com/2015/11/24/simple-autocomplete-with-elast…

If the data would be considered the customer's, it would have made sense to use application-level encryption [1]. Each user has a unique key which should be their property. If you need to give access to that data without the user's consent, you'll need to store their unique key for them. You'll better do that in a very secure manner. If now somehow the database gets exposed, good luck! You'll also need to get the individual keys to decipher everything. Then, although still you can be blamed for not using a vulnerability scanner, there is much less at stake. [1] https://www.compose.com/articles/encrypting-sensitive-data-in-your-mon…

^or the other IBM company whose name I can't remember I think you are referring to Compose[1]. We differ with/from the alternatives in a number of ways: - We have No rate limits. We do not limit the number of messages you can queue, the number of queues or any other artificial else. - All our plans are on dedicated server. We do not setup shared RabbitMQ servers(vhosts). - We do support HiPE (High performance Erlang). We have a comparison page[2] where we list more of these differences. 1. https://www.compose.com/databases/rabbitmq 2. https://www.amqphosting.com/us-vs-them

The oplog replication provided by Mongo is a very different mechanism than RethinkDB's change feeds. This is a pretty good overview of the differences: https://www.compose.com/articles/rethinking-changes-how-two-databases-…

It should be https://www.compose.com/articles/the-tool-we-built-to-help-us-work-rem… (found via search)

One thing that keeps me on CouchDB is Cloudant's pricing. It just destroys most of the competition. For example, the only RethinkDB hosting I know of is Compose and their pricing is $22/gb. Cloudant is $1/gb. https://www.compose.com/pricing#rethinkdb-pricing

Correct Fizz link https://www.compose.com/articles/the-tool-we-built-to-help-us-work-rem…

There is https://www.compose.com/rethinkdb

Compose | Remote (Canada, US, UK - Please see website for specific locations) What: Databases-as-a-service. We offer production grade, auto-scaling, automatically backed-up, add-on compatible MongoDB, PostgreSQL, Redis, and more. Hiring Process: Blind hiring! First, a light application. Second, all candidates who complete the application receive a work-sample resembling the work one would do in the role. No deadline. Final step is a work day. Compose has grown into a vibrant group where folks can feel comfortable being themselves, living a balanced life. We welcome you to enjoy comfort when taking risks, collaborate with spirited peers, and to unleash your creative and talented personality. * Work from home! * Many neat conundrums to solve. * Self-managing, distributed decision making. Choose your projects. We're deadline averse and quality focused. * Hardly any meetings. * Ruby/Go. * Fizz: https://www.compose.com/articles/the-tool-we-built-to-help-us-work-rem… Roles: * Database Team Member * Support Engineer * Visual Designer * Marketing Growth Specialist To begin: https://compose.interviewed.com

Well, there's always IBM: https://www.compose.com/postgresql

> secure and scalable > over the Internet What does this really mean? How does this substantially differ from the now-facetious term 'web scale' [1] ? Modern RDBMS'es offer encrypted communications between client and server [2][3][4], but nothing is stopping a deployer from putting a proxy between the database and the Internet-resident end-user to translate between authentication mechanisms. In fact, this happens in every single API today, where the Basic or OAuth or Cookie-Auth request comes in the HTTP body, and gets made into a database query in a query language the DB understands -- SQL or something else. GraphQL needs to you bring your own authn/z [5][6][7] much the same way that your run-of-the-mill HTTP API needs to you to bring your own authn/z, so I can't accept 'secure' as an innovation over SQL. "Scalable?" How? I genuinely think this tech is neat but let's consider what it gives you. GraphQL packages together the query language known as GraphQL, the IDL/typespec language known as GraphQL, the server spec known as GraphQL which a GraphQL-compliant server must implement [8], inside which you have to hook up your actual datastore to the GraphQL server [9][10][11][12]. It's a useful tool to build a client-server system where you're going to make a backend query in the end, but I wonder if its full potential will be realized when there are GraphQL-capable datastores to skip that extra data munging layer you have to implement yourself; but if SQL were passed on…

do you mean dbaas? https://www.compose.com/pricing https://aws.amazon.com/rds/pricing/ http://app42storage.shephertz.com/#pricing https://azure.microsoft.com/en-us/pricing/details/sql-database https://cloudboost.io/pricing there is one or two of them offer a free tier. anyone knows what is the most cheap dbaas for mysql? anyone knows what is the most cheap dbaas for mongodb? I'm a student. pls do check. My parents enslave me Pls help me. I wanna make apps so I can escape from this house

My company does managed Postgres on AWS, Azure, Google Cloud Platform, DigitalOcean and UpCloud - https://aiven.io/postgresql. Compose offers managed Postgres (https://www.compose.com/postgresql), as does ElephantSQL (https://www.elephantsql.com/). Database Labs is one more provider (https://www.databaselabs.io/). Google recently added beta version of Postgres to Cloud SQL as well (https://cloud.google.com/sql/docs/postgres/). Of course, AWS RDS and Heroku have been on the market for some time. I'd claim managed Postgres market is in a pretty good shape.