hackerm0nkey's comments

in short, grab a task. make it work, and never look back to make anything right.

I like the stability of Maven, despite XML and people complaining about it's complexity, I just find it stable enough and does the job quite well.

For one of my clients, we created lots of similar microservices, similar setup but slightly differ. What I did was creating a template using maven archetypes so spinning up a new microservice for a new piece of work or simply to try something out or an ad-hoc job is a matter of seconds, so setup time is stopped being a hindrance to start something new.

Also these days there are quite few tooling that supports project generators which can give you a bit of setup to start from.

Interested to see how you guys approached that for a Java B2B service. Thanks for the offer.

It's a template, GDPR is EU-specific and not everyone in the world has to worry about that, it's just too specific a subject to consider in a generic template.

If an EU-based (or storing EU data) team need to jump start from this, one can implement that section on top and not have to wait until the end as you say. The aim of the template is to give you a head start in the right direction.

I come more from a JVM world. But aren't there any DB migration/refactoring tools in Rails to allow for changes to propagate across tenants ?

E.g for the JVM, there's Liquibase and Flyway, and I agree with you, setting that up took a good part of a couple of weeks of dedicated effort.

On more than one occasion I've started with a simple table for all tenants (where tenant = x) because we didn't know at the time if we will have many.

Then progressively when we understood how the service will be used, refactored to keep separate tenant's data separate.

Ended up with each tenant in a given schema, we were using Java and relied on Hibernate (ORM) to help connecting to the correct DB (it does support multi-tenancy) as well as on a DB migration tool (Liquibase) so any changes we made to the schema get replicated over all tenants.

I have built many over the years in Java but nothing is public, I was thinking of abstracting away a Microservice template as a starting point for my projects.

What you are mentioning is a very specific example of that, happy to have a chat and perhaps we can build that together and open source it ?

I think the world needs, "Scala, the Good Parts". Hope this book is it.

I think they are both from the same author.

Yeah, I am getting the same impression that the personal might have ads? not sure.

I am trying it now and the trial version doesn't show me ads, at least not yet ¯\_(ツ)_/¯

Interesting, didn't know about SetApp before, thanks.

I wonder how they manage around DRM rights with the individual app publisher?

> After 1 year, you can continue using TablePlus without any limitations but you can't upgrade to the latest version. If you want to upgrade, you must renew the license, the renewal fee is much cheaper than buying a new one.

This sort of put me off. Personally I am fine with a single user perpetual license for my use case. But as they are claiming it being a young project and likely to have more bugs than your average mature product. Why do you expect me to renew my license to get your updates ? doesn't seem fair.

> TablePlus is a young project, we fix bugs and add new features every day, then put them together in a new update released at the end of week/month.

That week/month could fall a year after the date of my initial purchase :(

Ooh yeah. If you have ever integrated with Vantiv you will know what all this means. Heavy lifting is on the customer side. What a pain

Very useful article. Learned a couple of new things here.

While reading the idea that I know most of this, would that made me a data scientist? Jumped at me.

But then I quickly recovered from that thought that surely knowing some of the tools someone could use for a certain domain does not make you expert at that domain.

Might just be the case of same ingredients, different recipes.

Haha. That’s me. Once you go ‘set -o vi’, you can’t go back

yup, got the same reply back as well. Glad that our voice was heard

That's interesting, thanks for (re)sharing

fair enough, thank you :)

Great article and nice style distilling all this into a bite size chunks.

Is it me or just the title is a little bit inaccurate in the sense that there's more to "How containers work?" than overlays, e.g. it made me think that it covers more than it actually does, e.g. cgroups, namespaces, etc...

Anyone knows of a more in depth coverage of containers building block type of article that allows one to build a rudimentary container from scratch to appreciate what goes into building one ?

Yes, it's a welcomed side effect of TDD'ing, TDD is more of a design tool. But also I have experimented with writing tests before/after the implementation. Code with tests written first seemed to always be just to the point and get one in the mindset of thinking ahead of your edge cases and pin them down