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).
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?
The short answer is "no".
The high-level concept of AGPLv3 is to prevent someone who'd like to re-sell the OSS company's features (billing in our case).
For instance, let's say you're a vertical SaaS like Mindbody, selling software to yoga studio owners so that they manage their business: scheduling, payment, and billing.
If you use Lago to build your own billing feature (and sell it as part of your product), you'd need to either buy a commercial license (we call it "Lago Embedded") from us OR open source your code.
Let me know if you need more clarifications!
That is - offer your code to your customers under the agpl, not necessarily back to Lago or the community. But, since your customers get the code under AGPL, they in turn are free to distribute it. So, in practice, going that way - it generally makes sense to just open it up, and contribute back directly.
(imagine your only customer is IBM, or some other big company - they might not care/have an interest in re-distribution of the AGPL code - so you could be compliant (offer source to IBM) - but effectively closed off from the community).
As far as I understand it there's no legal precedent, so we're not completely sure. Some say calling an api means it's part of your application, meaning you need to open source your app. Some say that that's not the case. I think this unknown is why the license is banned in some companies.
I think what matters more is how the creators of the software intend the license. In case of Lago it's clear they want you to use it this way, and AGPL is only really meant to restrict businesses that want to fork it and start a proprietary billing service.
That's on point.
A "proprietary billing service", or a service that includes billing in the value proposition in general: whether you're a vertical SaaS, an accountingtech, or a payment processor.
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
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.
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)
I think this is a great recommendation for any new project that is considering to use Microservices. I like the approach of an in-memory event-driven system. This helps to enforce a message-only relationship between different conceptual parts from the start.
In fact, I did the same in one project. Also, while I am not covering Microservices in my book, the Sample Application uses a similar approach. The different contexts integrate via event communication. At first, this is an in-memory implementation and everything is running in a single process. Later on, it is replaced with a filesystem-based variant and the individual contexts are operated as individual programs.
How do you determine when "the need arises?" We've typically used bottlenecks, e.g. one piece of the app could benefit from additional scale while others wouldn't, and gone from there, but I feel like there's a better or more systematic approach that we're missing.
Do you use c# ? I let only application layers talk to each other for now. Also, i have some issues finding a decent saga to use that stores it's state ( eg. Something like the library Mass transit)
This is great approach. Implementing well-designed horizontally-scalable monolith app usually leads to keeping it monolithic for years, saving enormous amount of time, money and effort, keeping devs team compact and agile.
It's going to sound super simple, but initially you really just want to try and have as many conversations as possible with your users.
Firstly though, you need to have an idea (doesn't have to be perfect or 100% right) of who your target segment is. These are the people whose problem you are solving - and therefore initially are going to hold more weight with their feedback.
Once you have identified these users - use a combination of current users and potential users to get feedback from.
Some ideas:
* Email (like you've been trying) - Try and be candid and frank. Put yourself in their shoes - why should they respond? If it's a generic email their probably going to be of the mindset of either 'Someone else will do it' or 'I can't be bothered'. If you make it unique and more personal you're going to have a higher reply rate - but obviously a higher time commitment. I'd also suggest pushing for feedback calls rather then just messages. A call with a target user is worth its weight in gold.
As other users have suggested - offering a giftcard in exchange for a feedback call is also another valuable route if you can afford it.
* LinkedIn: Depending on your business (B2B or B2C) you can follow up with these users and potential new users on LinkedIn. Again this comes back to being somewhat more personal. Explain who you are etc.
* In app messaging: If they are constantly using your app - ask them while they are there in the midst of it. Don't be spammy though (this is approach we take mainly with delighted).
Lastly, once you have gotten your feedback - don't just take it at facevalue. Try and really understand what problem they are trying to solve as the solution might be completely different then the one they were thinking of.
E.g. if you were building an analytics app and someone gave feedback that they want to be able to export the data. If you take that at facevalue you will most likely build a tool that exports their data. However if you dig deeper and try and understand why they want to export the data, you might be able to solve a bigger issue for them AND for more users. E.g. if they come back and say they want to do XYZ with the data beacuse that means they can then gain ABC insight from the data - you might be able to add the ABC insight into the dashboard instead, skipping the need for export and customer work.
If you want more of a hand feel free to reach out! I'd be happy to help you out!
[1]: This is actually a problem we are trying to solve with Delighted so I feel your pain - https://getdelighted.co
Fluticasone changed my life, didn’t need allergy tablets, as it attacked the source.
Any generic brand works, just realize it takes like 10 days to start working, so be patient. Use as little as possible, so I recommend starting with 1 spray a day.
I mean the allergy tablets are attacking the source which is the allergic reaction just not very effectively. Fluticasone is very effectively and directly treating the symptom which is inflamed tissue in the nasal passage.
Anecdotes from my personal peanut gallery: Presumably after undergoing several adversarial attempts at amateur facial reconstruction in my earlier years, I've since endured persistent sinusoidal mysery, most notably an unreasonable susceptibility to colds. I tried many rational things which failed. However, it has been a (probably) irrational concoction that I've settled on, for 5 years now. A squeeze bottle of inert saline solution is thusly squozen and drip-fed a clean, high quality Lugol's solution (liquid iodine). At times, an essential oil is added too, eg peppermint, but rarely. At the risk of excessive iodine intake, my sinuses are now tolerable. Having doubts about this plebeian prescription, I encountered in my cursory research a patent by a prominent pharmaceutical company which consisted of the same recipe, but specifically for the "decolonization" of MRSA from the nasal passages. Considering that many folks now sport MRSA in their nasal passages, perhaps there's something to it. I've yet to settle on a suitable biofilm disruptor, but manuka honey is on my list.
If anyone is reckless enough to do the same, please thoroughly research the dangers of excessive iodine first. It is easy to err.
I had a persistent mrsa infection. Manuka honey worked better than prescription topicals. There are studies about the use of it for mrsa.
I never tried it deep in the nose though, only lower nostril. So it could still be higher up. But it hasn’t colonized the lower areas for years. Had it for 5+ years before realizing what it was.
Did you find that a UMF or MGO rating was important and if so, what was it? A lot of the manuka honey I see is quite low, and the few with higher ratings certainly reflect it in the pricing.
To be honest I’m not sure. I bought this medical grade manuka honey. That seems to be a thing, and it is sterilized for wound use.
Mind you I have no way of knowing if this is actual medical grade stuff that use in hospitals. But it seemed to work. On multiple mrsa outbreaks too: I had a few instances where it got outside the nose and this got rid of them.
What exactly are you doing with it? I wasn’t quite clear on how you’re going to get it deeper into the nose. I had had the mrsa in the lower nostril so I just used a q tip, but I didn’t get it into the nasal passages. (Nor do I know if it’s meant for such use). I also have congestion at night so I;m interested.
I will say that a jar like this lasts for many uses. If you’re eating honey it’s a small amount, but you don’t need much for topical use.
I would be irrigating the sinuses with it, diluted in warm (distilled!) saline water. I've done this with regular raw honey and haven't been too tempted since.
I am so trying that. I have to blow my nose quite often everyday and my nasal passages get frequently blocked especially when lying down trying to sleep. Fortunately, mucinex can fix that allowing me to sleep but fixing the source sounds better.
