243 karma · joined January 29, 2019
Yes if the live chat window is annoying you that you should buy something or sign up for a newsletter that is super annoying.
But if you really need help and there is a human within one second on the other hand this is amazing.
Also vice versa. If I'm online on Crisp or Intercom it is super easy to understand what my customer tries to do and help them within a second.
Not everything is negative about live chats, as always :D
Yes that is true and I think this is also the beauty of it. You can do anything with the code.
I know that one bad example often also is that you can change your CFN Template based on some external state (like an API) which can lead to some bad outcomes. But using a proper programming language can really speed things up a lot IMO
I used https://www.expireddomains.net/ in the past but their filter and UI isn't that great :D
Looks good. I'd like to see some more full examples
E.g. seeing the visual editor and the outcome of the terraform code then.
I also would be interested how easy it is to customize the terraform code then without it getting overriden by your system then.
I've submitted mine :)
Producer don't need to know to send it to which queues
Yes combining good content with advertising my product is the goal but I really focus on providing benefits with the content I create :)
Since I build on top of these great services I want to show at least how I am utilizing everything.
If you want, give ServerlessQ a try and let me know if you need any help! You find my contact info on my landing page: serverlessq.com or DM me on twitter: twitter.com/sandro_vol
But the whole point about costs with empty queues is important. It is definitely important to understand if you want to customize queues for example with long polling. This parameter changes the time your lambda will poll from your queue
Thanks for your kind words.
Regarding fanout. Yes exactly. Fanout doesn't mean it needs to involve SQS just it can involve SQS. It is also called a fanout pattern if you do a A2P and only notify Emails, SMS, etc.
To your second question how the architecture would look like for different preferences of architecture.
I think the main benefit of that architecture is that customer can subscribe to a topic. That means if your user A subscribes to the topic for Email and not in-app notification that is fine. It would be also just the one topic.
The consumer/subscriber has the power to subscribe and unsubscribe to topics (similar like you can to newsletters basically). That is one of the main benefits.
With a queue the producer would need to define which consumer will get the message and most probably it will be another application.
Does that help? :)
Good to know
Hashnode is the #1 blogging platform for developers that allows you to publish articles on your own domain and helps you stay connected with a global developer community. You own your content!
The two main tech roles are:
* Tech Lead: Be the first tech lead in the company, build up a foundation for a tech company
* Senior Software Engineer (Fullstack): Develop features & best practices with an awesome tech stack.
The tech-stack: - Fully deployed on Vercel
- Next.js, React, Tailwind
- TypeScript
- MongoDB
- AWS Serverless - CDK, Lambda, SQS, DynamoDB, Api Gateway
We love an open writing culture & transparency so you can share with the world on what you are working on.
Hashnode is hiring remote all over the globe (not just US only). We work async, that means you set your own schedule of working. You get dedicated time for writing your articles on blogs like the engineering or the townhall blog.Hashnode is backed by many great VCs (e.g. Salesforce Ventures, Accel Partners, Sierra Ventures, Sequoia Capital's Surge) and individual investors like Vercel's Guillermo Rauch, AngelList's Naval Ravikant, Intercom's Des Traynor, Ed Roman, and Salil Deshpande.
Please only apply if you consider yourself a good fit and are active on hashnode or any other blogging platform.
Contact me: sandro@hashnode.com / twitter.com/sandro_vol for more info or checkout the careers page: https://careers.hashnode.com/jobs
Contact me for any questions I am happy to help :)
I am not sure I am understanding what your tool is doing EXACTLY but the idea is good to have a platform for that :)
Instagram doesn't work for me and github names show available even when they are not. Other than that really cool.
If it gets enough traffic you can surely monetize it with some affiliate links to domain portals :)
Serverless search or on-demand search definitely makes sense. I would also be interested on what you use under the hood.
Also how can I define on what should be searched on?
Btw it says Munich is in Switzerland which is not true :D
Maybe as feedback what I understand:
* I click on MY email provider (e.g. Gmail)
* It redirects to my email provider
* Opens a new mail for that?