b0ti

8 ms·

1.
by b0ti 4y ago
Couldn't agree more. Not to mention timestamps that JSON simply doesn't handle and is essential for event data. The raijin database has an clever approach to solving the schema rigidity problem: https://raijin.co
2.
by b0ti 9y ago
NXLog - Log Management| DevOps Engineer | Europe | REMOTE ONLY | https://nxlog.co We would like to hear from you if you are interested in building fantastic products in the log management space and would like to be part of our g
3.
by b0ti 10y ago
I'm running a remote-only company and we moved to GitLab.com last summer from cloud hosted trac+git/svn combo (xp-dev). The reason we picked GitLab.com was because the stack is awesome and Trac is showing its age. We also wanted a
4.
by b0ti 10y ago
We are remote-only now so you can be located anywhere. The company itself is in the EU (Hungary). The careers page is a bit out-of-date, it will be updated soon.
5.
by b0ti 10y ago
We are also looking to hire a technical writer for NXLog. If you or anyone else is interested, feel free to reach out. https://nxlog.org/contact-us
6.
by b0ti 10y ago
The linked page already talks about jsonb in postgres. Feel free to read it! :)
7.
Show HN: Solving SQL's schema rigidity(raijindb.com)
5 points by b0ti 10y ago|2 comments
8.
by b0ti 10y ago
Note that this is not PG, Raijin is a new implementation and is not built on Postgres. Otherwise the question is valid. Raijin does not store NULL values though. In the above example a specific field (column) was selected and that's wh
9.
by b0ti 10y ago
Having to work with unstructured datatypes in Postgres and other RDBMS products was quite hard a few years back, now with hstore and JSONB in Postgres this has gotten much better but it still feels a bit unnatural. When we started the Raij
10.
by b0ti 10y ago
There is disk based buffering in NXLog CE. You might want to check it out with respect to the other woes you have with rsyslog.
11.
by b0ti 10y ago
You might want to consider NXLog if you need to do transformation at the source. For us this was an explicit design goal. Moreover it is also lightweight and a lot of people use it in place of other fat and bulky solutions, quite popular wi
12.
by b0ti 12y ago
I had a similar "open source burnout" recently. Since you asked for it, there is a blog post I wrote which might be of interest: http://nxlog-ce.sourceforge.net/why-the-gpl-does-not-work
13.
by b0ti 12y ago
> Why would you release something to the public and put your name on it if it's lazily done? No software is perfect. It has either no features in it or has bugs. The assholes will either demand to get the missing features added or t
14.
by b0ti 12y ago
Not sure about logstash but a lot of its users use NXLog ( http://nxlog.org ) as a shipper since it has a much lower resource footprint as there is no java and ruby in there. (I'm affiliated with NXLog.)
15.
by b0ti 12y ago
If you open source it, pick a license that's more restrictive (e.g. AGPL). This leaves a chance for you to get lucky and sell it to a company who wants it to use it as closed source so that you can buy a few beers. Otherwise they will
16.
Why the GPL doesn't work (well)(nxlog.org)
2 points by b0ti 13y ago|0 comments
17.
by b0ti 13y ago
Paid support is already there. There is a "support" menu on the webpage, the issue tracker has a polite note saying that this is available. Some people have been contacted directly in email to see whether they'd be interested
18.
by b0ti 13y ago
It's nice to hear about such success stories. Unfortunately most OSS projects never gain such a user base to be able to make a living off of it. I'm currently evaluating changing the license of our GPL-ed software to use something