Home > Erlang > Introspection hates functional programming

Introspection hates functional programming

Right now I’m trying to figure out a really good way to provide introspection functions in a functional language like Erlang. The point is that it is pretty useless to try to fetch internal states of processes since it disturbs the performance to try to fetch it. Think about it… trying to retrieve the internal state of a gen_server while it is heavily loaded.

Preferably you would have some data in an ETS table which you can print out or have a process which is specially for E.g. send update-messages two and then query that instead… but since everything is sending messages to that introspection process then querying it fails under the same argument as querying the first one.

I’m yet to find a “one-solution-almost-fits-all” concerning this, I always find myself either re-inventing ways or re-designing software to support introspection. You don’t realize how important maintenance functionality of software is until you are sitting there at 2-3 in the morning on a live system and a single introspection function gave you just the right information you needed to save your life.

The search goes on (da da dum da dum dum)….

Categories: Erlang
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: