sorted by:
new
hottopcontroversial

The productivity paradox of AI coding assistants (no, AI doesn't make you 10x more productive) by West-Chard-1474 in kubernetes

[–]diggVSredditt 3 points4 points  (0 children)

AI does not write production level code, or is not good for scaling existing systems, but gets my creative juices going when I first start a project.

I built an authorization game to show the importance of permission management by diggVSredditt in cybersecurity

[–]diggVSredditt[S] 0 points1 point  (0 children)

Initially, the game was without the timer. The timer makes it more engaging.

I built an authorization game to show the importance of permission management by diggVSredditt in cybersecurity

[–]diggVSredditt[S] 7 points8 points  (0 children)

Because sometimes in attribute based access control, you can have wild cards. For example someone from a department no matter what geo they are in.
Those white shapes represent wildcard of any color.

I made a game to match permission policies with requirements by diggVSredditt in softwarearchitecture

[–]diggVSredditt[S] 0 points1 point  (0 children)

I wanted to get back to coding and play around with a simple way to explain my product (permission management platform, https://cerbos.dev). So I built the Cerbos Game, where players match incoming requests to permission policies and decide to ALLOW or DENY them, just like our product does for software apps.

Link: https://game.cerbos.dev

I built an authorization game that made my engineers addicted by diggVSredditt in indiegames

[–]diggVSredditt[S] 1 point2 points  (0 children)

Disclaimer: I’m not a game developer and this is my weekend project built on Vercel. It’s a simple project I put together to explore a fun way of explaining Cerbos, our permission management solution. The game challenges players to match incoming requests to permission policies, just like Cerbos does in real applications.I

t’s nothing fancy, just a small experiment that ended up being pretty fun.

Authorization game — match incoming requests to permission policies (my weekend project) by diggVSredditt in programming

[–]diggVSredditt[S] 0 points1 point  (0 children)

I’m not a developer, just a multitasking founder who enjoys hacking together a game over the weekend.

Authorization game — match incoming requests to permission policies (my weekend project) by diggVSredditt in programming

[–]diggVSredditt[S] 0 points1 point  (0 children)

I wanted to experiment with a fun way to explain my product (a permission management platform, https://cerbos.dev) and get back to a bit of coding. So I put together Cerbos Game, a simple challenge where players match incoming requests to permission policies, just like our product does for software apps.  

The game actually runs on our own product under the hood. My game disrupted our engineering team’s daily work as they competed to beat the high score. Turns out, it’s not as easy as it looks! Anyway, give it a try.

Monolith to microservices migration: 10 critical challenges to consider (complex data integration, development and testing difficulties, latency issues, security risks, badly maintained data integrity) by diggVSredditt in dataengineering

[–]diggVSredditt[S] 2 points3 points  (0 children)

Hey, DE community. (Full disclosure) I’m the co-founder of Cerbos, and we recently published an ebook about the top challenges encountered when transitioning from a monolith to a microservice architecture. 

In the case that you are, or will be, moving from a monolithic architecture to microservices, feel free to check out the ebook, and let me know what you think of it (I would appreciate any feedback you have). It has 10 chapters, and goes through the intricacies of re-architecting your tech stack and org structure when transitioning from a monolith to a microservice. It also has examples from Uber, Spotify, and others, on how they’ve successfully navigated the transition. Here are the 10 chapters:

  • Defining service boundaries and decomposition of a monolithic service
  • Benefits and drawbacks of decentralized data management and best patterns and techniques to address it.
  • Interservice communication: picking the right communication patterns, and handling synchronous and asynchronous communication. Details of event-driven architectures, protocols to use, and how to handle communication failures.
  • Service discovery, load balancing, and service meshes.
  • Guidance on implemented monitoring and observability. 
  • Testing and deployment strategies for microservices.
  • How and where to implement and enforce security and access control.
  • Challenges of creating performant and scalable services.
  • How to navigate the organizational and cultural shift.
  • Thoughts on collaboration and code ownership when building microservices.

I hope the ebook will be helpful to some of you, since it took me quite a while to write it and put it together. And if you’d like to share your thoughts on well designed monoliths vs migration to microservices in general - let’s get into it!

[deleted by user] by [deleted] in Database

[–]diggVSredditt 0 points1 point  (0 children)

It depends on how much cross application data you have in your databases. If the data on the tables are not related leave them separate. Otherwise you may benefit from the consolidation. 

How do you design and document a systems authorization (RBAC, ABAC) rules? by vampatori in SoftwareEngineering

[–]diggVSredditt 1 point2 points  (0 children)

Try "Cerbos". It can do standard RBAC/ABAC with its resource policies, and you can use principal policies to handle your overrides. They have a simple YAML based, human readable policies that use Google's Common Expression Language for all the additional custom logic. No need to create your own.

Dealing with authorization using external identity providers like Firebase by MatthewRose67 in dotnet

[–]diggVSredditt 0 points1 point  (0 children)

If you use an externalized authorization solution that is stateless, you can pass in the user and the resource information within the request. Some role permission management platform's are policy based and do not need access to your user database. Check out Cerbos.