How much is it costing $ you guys to host parse server?

[jasan-s]

This is more of a discussion question. I would love to hear from people who have deployed parse server. I have looked and mongolab and heroku pricing. it seems it would run in hundreds$$. SInce parse shutdown announcement i have considered firebase but don't like the the non-pointer and querying json structure. Although firebase pricing is quite a bit lower than using mongolab+heroku option. How much is it costing you guys per month to host parse server yourself, and how much were you paying on parse.com.

[KudosGuy]

I am using VPS at local provider in Europe, because AWS price in Europe is like three times higher than US prices and also now the data have to travel smaller distance... I am on Ubuntu 14.04 and setup everything by myself with the digitaloceans guide... I am paing around 120 USD per year for 30 GB SSD storage, 100 Mbps unlimited network and 1 thread Xeon 1.70 GHz... memory is good but I am not sure how much request this CPU can handle...

[steven-supersolid]

This is something I've looked in to as part of load testing, but only at the high end. My setup is Heroku + mLab (not using the mLab addon as that is more expensive).

I achieved around 600 requests/second split evenly between Cloud Code call, database read, database write, with:
1x Heroku Performance L dyno (has 8 cores, capitalise on this with Throng) = $500/month
mLab Dedicated M1 Standard cluster = $180/month
Total = $680/month, equivalent Parse.com cost = $5700, so 12% of Parse.com price
This was pushing the limits of the hardware but even using 2 dynos and mLab M3 HP we are looking at $1000 + $1390 = $2390 per month, so 42% of Parse.com price.

If fewer requests/second are required then we could drop the dyno type down to 1 Performance M at $250/month but I found these to only have 2 cores, so not the same value as Performance L. The advantage of the Heroku Performance line is that they are dedicated instances, but this is not what we get on Parse.com so we could lower costs by dropping to Standard 1x and 2x at $25/$50 month per dyno respectively. Choosing the Hobby dyno type with mLab Shared Cluster will result in costs of paying tens of dollars per month and there is a free tier on each.

What I've not factored in is the behind the scenes service we get on Parse.com where the team of ops and backend engineers keep things running smoothly with the platform. Building your own setup on AWS is going to be the cheapest but then you have to maintain it. I chose Parse to avoid that. I've not used the support at Heroku but the mLab support is amazing.

[jasan-s]

wow , it does seem for a MVP of a product, firebase will be a lot more cost effective

[otymartin]

I deployed to app engine. So far as the only user of my app deploying my server 10 times a day, I racked up around 55USD in a month. Luckily I'm using 300dollars in free credits but its still not a good thing. Im hoping the problem is on my side because sometimes app engine/compute engine spins up like 8 instances while remember, Im the only one using my app (Messaging app).

[flovilmart]

Disable auto scaling, delete / stop unused versions

[jasan-s]

Actual $ amounts for comparison will be helpful
On Mar 24, 2016 4:01 PM, "Amisalabs" notifications@github.com wrote:

There is huge cost savings from using Nodechef's managed parse server and
mongodb. Nodechef actually uses mongorocks so compressed storage saves you
money. Pricing is also cheap when compared with Heroku/mlab for small and
big data considering Nodechef provisions containers on bare metal servers.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1174 (comment)

[noder199]

@jasan-s firebase is gonna disappear at some point, Google does this with a lot of their acquisitions.

[jasan-s]

I am afraid of that as well but for a minimum viable product for an app I
am hoping it lasts long enough and hope they offer migration similar to
parse.com. I loved parse but with all the comments it seems for a product
that still needs validation . firebase is more economical initially.
On Mar 24, 2016 9:03 PM, "noder199" notifications@github.com wrote:

@jasan-s https://github.com/jasan-s firebase is gonna disappear at some
point, Google does this with a lot of their acquisitions.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1174 (comment)

[harrygt]

T2 Micro Instances on Amazon AWS and auto scaling with Mlab.com free tier database. It's about $25 a month which is fine for a small usage app. If you're new to Amazon then you get a free years usage on those settings.

[Knana]

For many apps, the $9 cluster (1 GB database and 128 MB app containers) from Nodechef is adequate. The below example uses a news aggregation app which is doing ~100 req/sec
The Parse Server boots at around 65 MB of the app memory so you have around 63 MB left. Most requests read around 30 rows maximum. When rows are batched as in 30 rows to show on a page, they barely exceed 1 KB per row. And when the article is actually displayed, that row does not exceed 32 KB. Since the row has to be in memory before it is transported, you can simply calculate (100req/sec x 1 KB) which is not even 1 megabyte of memory. Note that req/sec is mainly on the database size and Nodechef's SSD and mongorocks setup is fast.

I work at Nodechef and we provide a fully managed Parse Server and MongoDB with the RocksDB storage engine.

[flovilmart]

@Knana thanks for being awesome 🏆

[otymartin]

@flovilmart how do i disable auto scaling on app engine?

[flovilmart]

Check the app engine documentation, Python docs on app.yml particularly

[FridaySG]

@Knana would like to hear more on the fully managed side of things. So if I provided an S3 setup to use with the FilesAdapter you guys could make that happen?

[stephanelpaul]

i use two instances of digitalocean, one for the mongodb and one for the app, for files management i used s3, its not costing me more then 40$ a month.

Although i'm working on a postgresql adapter will be using amazon rds.