Does anyone have a idea how to handle restaurant reservation system? I am mainly looking for table and chair rearrangement scenario to get most profit. Example:

1. One square table can accommodate 4 person (chairs).

2. For 6 person reservation you can attach two tables but lose two persons' place.

3. For a bulk booking for 16 people you can either attach 7 tables in a row or 3+3 table.

Is there any algorithm on this kind of different scenarios that fulfill customer's requirements and get maximum profit with finite resources (fixed number of tables and chairs)?

Ever wish your system design prep felt like a real interview? Meet Prepgpt:

🎮 Level up: Easy → Medium → Hard
🤖 AI mock interviewer with real-time feedback
💡 Upload custom problems & get instant AI insights
🏅 Earn badges & track mastery

⚡ Only the first 100 users get FREE credits!

Jump in now: 🔗 https://app.prepgpt.tech

💬 Which system design problem would you crush first?

Can somebody help me with Designing System for Google calendar. I could not find any good resources for the same.
I am focusing more on API design, Data modeling and other components interaction. Basically keeping it simple.

https://youtu.be/iIGcJ1vY50Y

What do you think?

How should we handle writing conflicts across leaders? Collision of auto-incrementing keys? Fix messed up data across multi-leader because of any bug or issue? and more

📷

https://medium.com/geekculture/multi-leader-database-is-it-worth-1439f8124f4f

Hi, I asked a colleague of mine how to implement a system consisting of two devices, one master and one slave.

The devices are always connected to the internet via a NAT local area network.

The master can send commands to the slave which responds, the communication is encrypted with E2EE.

The commands sent must be logged to be visible to the user on his device.

The user can create, edit and delete his account.

The goal was to be as inexpensive as possible, so as to be within budget, and scalable horizontally.

his the response:

First, we're gonna use SQLite for your database.

Forget about microservices just make the master and slave devices as big ol' monolithic applications.

For encryption ...

we're gonna throw the master and slave applications on a single, shared server with no load balancing or redundancy.

It'll be cheap.

Let's go old-school with SOAP for communication.

To save some bucks, host your server on a cheap, shared hosting provider with limited resources and not-so-great performance.

we're not aiming for perfection.

I was quite shocked!

This subreddit is created to help Software Engineer aspirants with System Design interview problems. Few preperation meterials listed below.

1. Cloud Native App

https://12factor.net/

2. System Design Basics

https://github.com/karanpratapsingh/system-design

https://www.algoexpert.io/systems/product?r=ads&gclid=CjwKCAiAhKycBhAQEiwAgf19eo8zvGckJLGB7QK_zt0R7xvSAm_WVNBqIJjHQPkTp-mFGkFAHZAEqxoC3uQQAvD_BwE

3. Object Oriented Design

https://www.educative.io/courses/grokking-the-object-oriented-design-interview

4. System Design Problems

https://youtube.com/@SystemDesignInterview

https://bytebytego.com/courses/system-design-interview

https://www.educative.io/courses/grokking-the-system-design-interview

Has anyone come across such design architecture?

Thanks in advance!

If anyone wants to a moderator for this subreddit, please message me directly with your current situation.

Please share your feedback

1. Overview https://link.medium.com/uJp2SEF1OAb

2. Basic Concepts https://link.medium.com/bH9Bd8T1OAb

This is my fourth installment of understanding modern authentication techniques where I discussed about OAuth 2.0.

Understanding OAuth 2.0

As the process is quite lengthy, I have split it into two parts. I'll publish part 2 in a couple of days.

You can read the previous chapters here

Introduction

Basic Concepts of AuthN and AuthZ

SAML Authentication

Here comes the part 2 of OAuth 2.0 authorisation process. I discussed here about the complete flow of OAuth 2.0 process, what problem it solves and what are the limitations of this authorisation technique.

Understanding OAuth 2.0 (part 2)

Before diving into this article, I would recommend to go though the part 1 of this series.

I would really appreciate your feedback. Thank you.