What is your project about? I'd setup an automated pipeline which deploys your code automatically on each git push. You can check out buddy for example for that
Docusaurus is really fun to work with. Nice and fast, super configurable, and excellent documentation! If you're used to React it's a no-brainer, the sky is the limit.
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
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
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.
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.
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.