HN user

jack335

243 karma

twitter.com/sandro_vol

Posts50
Comments59
View on HN
cremich.cloud 1y ago

Don't let Technical Debt sabotage your product roadmap

jack335
2pts1
stellate.co 2y ago

Launch Week: GraphQL Insights with Stellate

jack335
1pts0
blog.jannikwempe.com 2y ago

Different Node.js Versions and Package Managers per Project – A Solved Problem

jack335
1pts0
alexkates.dev 2y ago

Yes, You Should Use TypeScript

jack335
3pts0
blog.jannikwempe.com 2y ago

Podcast Notes: Minimal Empires

jack335
2pts1
townhall.hashnode.com 2y ago

Hashnode Public APIs 2.0 closed beta

jack335
1pts0
www.youtube.com 2y ago

Principles for Scaling Front End Application Development [video]

jack335
2pts0
www.youtube.com 2y ago

Books to Learn AWS Cloud [video]

jack335
2pts0
engineering.hashnode.com 2y ago

Crafting Superior APIs with Design Guidelines: Set Up for Success

jack335
2pts0
blog.sause.dev 3y ago

Use Clerk, SST and a JwtAuthorizer to Secure Your API Gateway

jack335
2pts0
www.10printiamcool.com 3y ago

Encapsulation Is Not Always Desirable

jack335
1pts1
blog.leapp.cloud 3y ago

Identity and Access Management in Multi-Cloud Environments

jack335
2pts0
kentcdodds.com 3y ago

Stop Being a Junior

jack335
18pts23
sandeep.dev 3y ago

Mistakes to avoid while recruiting for your startup

jack335
4pts0
blog.jannikwempe.com 3y ago

Porting a Shopify Store from NextJS to Shopify Hydrogen

jack335
1pts0
blog.cloudaffle.com 3y ago

The New TypeScript Satisfies Operator

jack335
2pts0
blog.jannikwempe.com 3y ago

Debunking Tailwind Counterarguments

jack335
1pts0
tigerabrodi.blog 3y ago

Pair Programming for Remote Teams

jack335
2pts0
reviewpad.com 3y ago

From Readme to Docusaurus: How an Intern Saved Us $1.2k

jack335
11pts12
blog.awsfundamentals.com 3y ago

Infrastructure as Code on AWS – An Introduction

jack335
4pts2
marcotroisi.substack.com 3y ago

The Beauty of Cloud-Based Development

jack335
1pts0
blog.jannikwempe.com 3y ago

AWS Is Different. What Are AWS Accounts, IAM Users and Root User?

jack335
1pts0
www.brev.dev 4y ago

Don't Let a Bad Abstraction Cost You 2 Years

jack335
2pts1
dx.tips 4y ago

The Radiating Circles of Developer Experience

jack335
3pts0
blog.thecode.xyz 4y ago

Pareto Principle for Software Developers

jack335
3pts0
blog.matteomortelliti.com 4y ago

Add Feature Flags to Your NextJS App Using Firebase’s Realtime Database

jack335
1pts0
blog.suborbital.dev 4y ago

Tour of the WASM Ecosystem

jack335
2pts0
blog.100daysofcloud.com 4y ago

Building Real-Time Serverless Web Applications with API Gateway WebSockets

jack335
1pts0
www.alexdebrie.com 4y ago

The Three DynamoDB Limits You Need to Know

jack335
2pts0
blog.esteetey.dev 4y ago

How to create and test a GitHub Action that generates Supabase database types

jack335
2pts0

I think that depends heavily.

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

Thanks!

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

Cool that you revamped a bit, I've tested digger.dev once with you!

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.

Yes this is the fanout pattern - called at least in AWS context. It is pretty normal to use it like that to decouple it even more.

Producer don't need to know to send it to which queues

Thanks!

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.

Thanks a lot!

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

Exactly. SQS is a queue where a message resides. Lambda basically polls this message. But like kondro said basically it doesn't matter (directly). I think it is important to understand the event source mapping takes over the polling. But in the end it looks like a push system.

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

Hi author here :)

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? :)

Hashnode | Fully REMOTE & Async | Full-Time Multiple roles (Engineering, Design, Product)

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 :)

Looks really cool and useful +1

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 :)

This looks pretty cool! I like the idea of managed databases and getting access via an API layer.

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?