Paulo Renato

Video Pundits Video Pundits transforms the way you watch Youtube videos to learn, research, take time-linked notes and to bookmark key insights

Video Pundits - Be the Pundit of your notes.

Take time-linked notes and bookmarks on Youtube videos at https://videopundits.com.

#MobileAPISecurity #VideoPundits #Youtube #Videos #Notes

Home | Mobile API Security Mobile API Security Consulting: Let's connect to discuss how I can help you secure your API and Mobile App with a 360 Shift trategy.

Checkout https://mobileapisecurity.com.

#MobileAPISecurity #APISecurity #APIS #MobileApps #APISec

BEAM Devs Your Gateway to the BEAM Ecosystem - A network hub for developers, companies, and recruiters to showcase projects, share knowledge, and find the best talent in the BEAM world.

Check out https://beamdevs.com - Your Gateway to the BEAM World!

#BEAMDevs #ElixirLang #ElixirPhoenix #Erlang #GleamLang

Not yet, but will be free for a lot of things and paid for others, like to advertise jobs. I may have a free tier and a paid tier for networking, but not sure yet. The first thing is to get traction, next to get sponsorship and if the income from it is good I may only charge for advertising jobs.

👆 Visit beamdevs.com and subscribe for updates and/or early access as Alpha and Beta tester.

🎯 My target is 1,000 subscribers by the end of March. Otherwise, I will assume the community doesn’t have enough interest in the project. If you want it to become a reality, just hit that subscribe button

👆 What actions would you like within the BEAM Devs Network❓

For example, follow, connect, share and ...

✅ Don't miss your chance to shape BEAM Devs with your suggestions 👇

✨ Like and repost to your network

🎯 Follow me to not miss the next update

#BuildInPublic #ElixirLang #Erlang #GleamLang

👆

Individual profiles will have a different structure from company profiles.

What info would be the most important for you to see in an individual and company profile❓

Bonus points if you can tell from which perspective, dev, team lead, CTO, hiring manager, recruiter, just to name a few.

👇

👆

To enable effective networking and easily find matches for who you want to connect with, profiles for both individuals and companies will be strictly structured. When creating a profile, the majority of its fields will need to be filled by selecting from a predefined list of one or more options,

👆

BEAM Devs goal is to enable developers and companies to network with others to find projects they can collaborate on, whether open-source or not, and to share ideas and knowledge in closed groups or publicly.

👇

📢 BEAM Devs dot com: Your Chance to Shape BEAM Devs Functionality

At the core of #BEAMDevs will be the network of developers and companies using the BEAM ecosystem, whether with Elixir, Erlang, Gleam, or another language running on the BEAM VM.

#BuildInPublic #ElixirLang #Erlang #GleamLang

I agree that the LSP experience is far from perfect and a huge adoption bottleneck for Elixir adoption, but I am curious about what other tools were difficult for you?

BEAM Devs Your Gateway to the BEAM Ecosystem - A network hub for developers, companies, and recruiters to showcase projects, share knowledge, and find the best talent in the BEAM world.

👆 If this project resonates with you then don’t skip to subscribe now for updates and/or early access at:

beamdevs.com

👆 What would you do differently?

Do you have any questions or suggestions?

👉 Share your thoughts and suggestions below

✨ Like and repost to reach your network

🎯 Follow me to not miss the next post

#BEAMDevs #ElixirLang #Erlang #Programming #SoftwareEngineering

👆 Also, In software development, you can choose the fast lane and build tech debt to ship faster, or you can choose the middle lane to balance speed with quality, my option.

Otherwise, new features and bugs will become increasingly difficult to work on as the project grows via the fast lane.

👇

👆 I could start with a non-distributed traditional Phoenix app, but I want to use this project as an opportunity to use distribution for real, and to start with a good base for building a very resilient architecture.

👇

👆 So, my challenge is to be able to use the failover and request duplicator approach in conjunction with blue-green deployments and keep strong consistency guarantees for my CRUD application.

👇

👆 As with everything in software architecture, it's about trade-offs. Thus, this will have some, like added complexity to ensure no side effects occur in the non-production systems and to guarantee that both production and failover are in the same state (strong consistency).

👇

👆 I am thinking of using this approach for BEAM Devs, as per the diagram. However, I have a CRUD application from the user perspective, whereas in my previous roles, they were read-only for external users and CRUD internally based on background jobs or request metadata collection and analytics.

👇

👆 Bear in mind that I wasn't in the DevOps team, nor did I have input on the architecture. Thus, the diagram in the start of this thread is trying to reflect what I was aware of and can recall.

👇

👆 Key Consideration: Applications using this approach must ensure side effects (e.g., emails, billing) only occur in production. A flag-based system is required to enforce this.

👇

👆 The request duplicator only relied on production responses but on my case it could be coded to consider the first response from production or failover. For strong consistency guarantees, it could wait for both before returning a response, backed by a TTL and a request failure-handling strategy.

👇

👆 In my second role, we had a request duplicator.

This tool allowed stress testing of new releases by amplifying live requests (e.g., x2, x4) to find breaking points. It also helped validate major architecture changes before going live by running them in parallel with production.

👇

👆 Failover isn't the same as Blue-Green Deployments.

While a blue-green deployment gradually replaces an older version, failover runs continuously alongside production.

Ideally, both strategies should be used together when possible.

👇

👆 When a cloud provider is having an outage/issues or we have a production incident that is not easy to solve or roll back effortlessly, we can switch the DNS to use the failover system, or having clients switch automatically to the failover when production doesn’t respond after a certain timeout.
👇

👆 This differs from redundancy within the same provider.

In this approach, the switch from production to the failover happens by manually switching the IP for the server in the DNS, which has a very short TTL.

👇

📢 #BEAMDevs app: Asking for Feedback on my Software Architecture Draft

In my first two UK roles, software architecture always included a failover system, an independent, exact copy of production running in another cloud or on-premises data-center

#ElixirLang #Erlang #GleamLang #Devs #Programming
👇

The BEAM requires another mental model to take advantage of it's superpowers.

It's easy to start with, but to take fully advantage of fault-tolerance via well structured supervision trees and use of message passing takes time and effort.

👇 Are you aware when to use an not use GenServers to avoid bottlenecks?

I use MailerLite to collect the emails, thus you need to thank them :)

I recognized you immediately in the list and was surprised with your email format, and to be honest I never saw one similar.

BEAM Devs Your Gateway to the BEAM Ecosystem - A network hub for developers, companies, and recruiters to showcase projects, share knowledge, and find the best talent in the BEAM world.

👆

Visit the website and subscribe for updates or just early access as Alpha and Beta tester.

beamdevs.com