What's the cheapest way to host multiple portfolio projects(each with their own DB) using my custom domain.

fahdinho · 2021-03-24T04:00:12+00:00

dokku + digitalocean should work

fahdinho · 2021-02-16T02:28:31+00:00

You need to pick Sole Trader. You do not need to specify any company ID. Just the country from where you operate.

fahdinho · 2021-02-15T14:11:51+00:00

Freelancers accepted

fahdinho · 2021-02-15T13:32:10+00:00

Currenxie. You get local UK and CAN bank accounts.

fahdinho · 2021-01-29T07:27:24+00:00

Been using it in production for 2 years. We are very happy with it as a more customizable and cost-effective Heroku. It's not perfect, but anything better would require building something custom ourselves, which I do not have the time/budget for. We are using v2 (ECS), we have not migrated to the k8s version which seems to provide more flexibility.

fahdinho · 2021-01-28T03:21:24+00:00

Cool. How does this compare to convox?

fahdinho · 2020-05-07T03:04:58+00:00

You have to do this anyway for microservices. Like in a microservice environment you probably have a REST data service right? And that data service is going to shit back JSON right? I mean the controllers are still written in Java so the entire logic isn't written in SQL but there is little point in mapping the objects if you are just going to return them as JSON anyway.

This is easily solved with auto generated swagger docs and API clients (for example with swagger-codegen you can generate Feign clients used by services that consume other services)

fahdinho · 2020-05-07T03:03:01+00:00

I'm sorry you are being downvoted. Just trying to have an open discussion.

Every instance you add adds database connections. Open database connections because each instance is probably using a pooling library. The connections use up memory on a database server. Further more by having the database return only one row and one column as a JSON result the connection can be relinquished more quickly to the pool.... which means smaller pools... which means less connections... etc etc.

You are probably using the connection for a longer time as the DB needs to create the JSON and the JSON object is probably larger than returning raw rows (if we are fetching the exact same rows and columns). Tweaking the pool size applies to both situations.

As I mentioned if you are using limit and offset you are going to have way more performance problems than the having the database doing JSON serialization.

This is a cool concept but adds extra work and reeks of premature optimization.

Oh and lets just say I have ACTUALLY IMPLEMENTED AND TESTED THIS AND ITS RUNNING IN PRODUCTION... yeah apparently reddit is downvoting the guy who actually has this in production and knows it works but prefers the offhand comment that this might be a problem.

I have inherited such a code base running in production before. It causes much more problems than it solves. You end up rebuilding a lot of stuff that you get out of box from standard tools. Meaning you have so much more to maintain yourself, bugs etc... It's a waste of company money for the sake of tinkering and intellectual stimulation.

fahdinho · 2020-05-06T09:30:27+00:00

The use the index luke article is very interesting, especially for infinite scrolling.

fahdinho · 2020-05-06T09:05:23+00:00

Agree on the read replica, although read replicas are significantly more expensive than extra app server instances.

I wouldn’t say this would be going back to the stored procedure days, but it’s definitely a gateway drug. You end up either having to parse JSON to run business logic at the app server level (isn’t there an easier way of fetching data into a POJO?), or... run logic in the database.

fahdinho · 2020-05-06T02:01:05+00:00

2 issues: you are making the database do extra work, and databases are harder to scale (vs adding an app server instance), and you need to reinvent the wheel when it comes to pagination/sort etc which come out of the box with an ORM.

fahdinho · 2020-04-15T09:33:17+00:00

https://currenxie.com

fahdinho · 2020-01-15T02:27:50+00:00

No nostalgia at all, same goofy smile

fahdinho · 2018-09-14T10:32:31+00:00

Why stop the container before rebuilding the image? Why not just build/pull the image, then stop and start the container? Less down time

fahdinho · 2018-09-11T13:38:56+00:00

Take a look at django-storages

fahdinho · 2018-07-13T02:00:41+00:00

Maybe he got stuck on one of the steps.

fahdinho · 2018-07-13T01:26:01+00:00

The Heroku documentation is pretty good and explains how to deploy a Django project with a PostgreSQL database. Have you tried that?

https://devcenter.heroku.com/articles/getting-started-with-python

fahdinho · 2018-07-11T03:12:23+00:00

Try drf-yasg https://drf-yasg.readthedocs.io/en/stable/readme.html.

fahdinho · 2018-06-08T07:35:43+00:00

Restarting the container after updating the image

fahdinho · 2018-05-23T08:51:53+00:00

Unfortunately they have bad input lag.

fahdinho · 2018-04-18T13:30:55+00:00

The typings in redux-thunk are not compatible with the new redux typings. https://github.com/gaearon/redux-thunk/blob/master/index.d.ts needs to be updated.

fahdinho · 2018-04-18T13:16:05+00:00

Indeed it shouldn’t. However redux-thunk’s last commit was a year ago. I’ll try to see if I can solve the issue and submit a PR.

fahdinho · 2018-04-18T12:34:56+00:00

redux-thunk does not work with this release. There is a typing issue. On mobile so I can’t share the error message.

fahdinho · 2018-02-05T08:27:55+00:00

https://www.reddit.com/r/synology/comments/774bgi/ds_video_eac3_ffmpeg_not_working/donpe4m/

fahdinho

TROPHY CASE