News for hackers. Stuff that matters.

edgurgel

Re:Keycloak SSO with Docker Compose and Nginx on Sunday February 11, 2024 @03:03PM (#39338112)
Interesting... I had the exact opposite impression. The codebase is big but very easy to understand and their SPIs[1] enable to customise Keycloak's behaviour quite easily.

For the statefulness using terraform[2] solves the problem for me.

[1] - https://www.keycloak.org/docs/latest/server_development/#_pr... [2] - https://github.com/mrparkers/terraform-provider-keycloak

Re:Auto-Scaling and Self-Defensive Services in Golang on Sunday March 27, 2016 @03:38AM (#11369245)
Virding's First Rule of Programming

"Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang."

http://rvirding.blogspot.co.nz/2008/01/virdings-first-rule-o...

Re:Verk – An Elixir job processing system backed by Redis on Wednesday March 09, 2016 @10:19PM (#11257225)
Here's a detailed explanation: https://github.com/edgurgel/verk/issues/2
Re:Verk – An Elixir job processing system backed by Redis on Wednesday March 09, 2016 @10:03PM (#11257182)
That's a great question. I chose Redis for 2 reasons:

* Simple to use

* Compatibility with other systems like Sidekiq/Resque. Out of the box it will understand their clients.

My experience with Mnesia is close to none but I know it's not trivial to deal with split brain scenarios for example. It's also complicated to connect multiple nodes for my use case (using docker) and also to deal with moving instances inside a cluster. I would need to care about the locality of the data.

One can use any Redis service (AWS Elasticache, Redis Labs) and not care about maintaining a database. The Verk user just needs to have a working Redis database.

I'm pretty sure that having the database in the same space as the job processing system would speed up things. I would love to see a project that tried this approach. Probably not using JSON but simply Erlang terms.

Re:Verk – An Elixir job processing system backed by Redis on Wednesday March 09, 2016 @09:36PM (#11257116)
OTP won't out of the box persist jobs that you want to guarantee that it will run. It won't also retry and it can't schedule jobs to happen in the future.

Unless you are willing to lose the jobs that are just in memory you can simply use Task and send messages.

RabbitMQ also does not handle retries with backoff, scheduled jobs, etc.

Disclaimer: maintainer here.

Edit: I added the "with backoff" to not mix with automatic reenqueue if you reject a message from a Rabbitmq consumer.

APNS2 has a simpler interface and doesn't do things like generate website packages etc. APNS2 has better test coverage, and handles errors in a more go-like way. (Returns a response if a documented response was received from Apple, or an error where an unexpected error occurs.)

We are running this in production at http://carnival.io to send millions of notifications, to my knowledge buford has not been tested in production yet.

He will be here: http://www.erlang-factory.com/sfbay2015 . Hopefully he will share his thoughts.
Re:What can I only do in Erlang? on Friday November 07, 2014 @05:16AM (#8571875)
I like this blog post (http://blog.erlware.org/some-thoughts-on-go-and-erlang/) as it talks about some of the differences about them. For some of these reasons I don't think they solve the same issues and one won't eat the other.
Re:Elixir v1.0.0 released on Thursday September 18, 2014 @10:25PM (#8338713)
A Pusher server clone: https://github.com/edgurgel/poxa
Re:Elixir v1.0.0 released on Thursday September 18, 2014 @04:35PM (#8337487)
Re:Poxa: A Pusher clone with a real-time Console on Sunday April 20, 2014 @02:24AM (#7616059)
Yeah they "endorse" if you consider they published a link to Poxa here: http://blog.pusher.com/pusher-community-libraries-highlights...

Thanks for pointing out Fanout. Looks like a nice product/project.