harrylucas
Joined 10 years ago
Karma
90
Submissions
47
Member since
Sep 12
Recent submissions
Comment · 2 years ago
Wanted to check if this actually provides a unified api? E.g. each category of integration will return the exact same data shape? From the looks of the video I'm still making a call to slack's API `users.list` and have to write the code to paginate slacks api (e.g. the next cursor).
Comment · 3 years ago
It's much simpler then that. The answer is 100% on the home page though
Comment · 3 years ago
I always get confused with AGPL and seems to have differing opinions online, so wanted to ask here. If I use Lago in my app, and don't change it all, do I need to opensource my entire application?
Comment · 3 years ago
Yeah instantly my thought. Also since it’s only in “request access” mode it’s not something that can be ticked off eg not really apart of the list. Also the landing page for it feels like it’s written in the same style.
Definitely not against advertising the product but make it more explicit
Comment · 5 years ago
Metomic | London UK | Full-Time, Remote-OK (UK Hours) | https://metomic.io | £75-£110k
Metomic helps companies discover and control their sensitive data footprint across their cloud applications. We're an engineering first, data driven company looking to change the way companies manage and protect their sensitive data.
We're looking for a range of front and backend engineers to help us scale out the platform. We're looking for individuals who are pragmatic, value good communication, respect and innovation.
Frontend: https://app.otta.com/jobs/RElTazIx Backend: https://app.otta.com/jobs/cFBzNWFy
You can also reachout to michelle <at> our website domain for any questions
Comment · 5 years ago
[Backend+Frontend Roles][London, UK][£75k - £105k]
Hey !
We are hiring both Backend/Fullstack and front end engineers at metomic (metomic.io).
At Metomic we're out to change the world data privacy and compliance by giving companies the power of data without the risk.
We are in early stages but have some great traction and a very exciting couple of months ahead of us here.
Tech we use:
* Frontend: React / Typescript * Backend: Typescript Node (most likely will change), Docker, Neo4j, Postgres, RabbitMQ, ECS + Terraform.
If it also matters - we are much more towards the FP side of the scale when it comes it FP vs OOP.
Checkout our jobs here if you are interested:
*Backend/Fullstack*: https://app.otta.com/jobs/cHFyZ09p *Frontend*: https://app.otta.com/jobs/WE5VNkdi
Comment · 5 years ago
This is really the big problem with DDD microservices. Whilst I'm a huge fan of the two, my go to is to always start out with a monolith and enforce boundraries within the application that could potentially become microservices at somepoint in the future. Even go as far as to use an in-memory event-driven system in the monolith. Then and only then when the need arises do we pull it out into it's own microservice.
This has various benefits but the biggest one being you get to play with the design of the 'microservices' before actually committing to making them microservices allowing you to make better informed decisions. The harder part is that it does require stronger discipline and if not done correctly, a harder transition to microservices (e.g. pulling out the components)