saas | SaaS business with SaaS boilerplate

Webpack throws an error

I am trying to use the Netsuite Rest api. Below are the steps I took. https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_162730264820.html

1. Created a Integration Record in Netsuite

2. Create a self signed cert:

   ...

We have Spring Boot projects that we wrote Rest API.We started to actively use aws. We are moving to the Saas structure and we want each client to define their own policy. For example, we have an API with the /getUser endpoint.Some of the tenants can create the "xxx" role. It can request users in the xx role to access this endpoint.Other tenants create the role "yy". It may not want users with this role to access the "getUser" endpoint.Is there a structure where tenants can define roles and manage dynamic these roles in endpoint style? Is there a framework that can solve this issue?I have used keycloack and spring security before. I can't come up with a simple solution using these

Actually, I have a request. Let me authorize tenants using the app. This user can define roles. Let my API endpoints group and create a role. Is there such a structure or what should it be?

We have a repo (SaaS project) that contains a list of branches (50-100), the master branch is up to date, So I want to open a list of PRs for every branch we have to take updates from

master -> client-*

So is there a way to handle this case automatically?

I'm new to AWS and it's services. What I want to achieve is a multi-tenancy SaaS application. What my concept looks like: I use Cognito for user authentication. There all users no matter what tenant they belong to should use one frontend to login. For the tenant-recognition I use a custom attribute "custom:tenant" which I get from the JWT when the login is successful. For the applicantion itself I want to use VPCs and to ensure encapsulation each tenant should have their own VPC.

Example:

• User A of Tenant 1 login and gets back JWT with claim "custom:tenant":"1" should be routed to VPC 1
• User B of Tenant 2 login and gets back JWT with claim "custom:tenant":"2" should be routed to VPC 2

Now my question is: how do I achieve this routing from the success of the login to the appropriate VPC? Do I need further Services for that or where do I find these settings?

We're currently developing a SaaS platform (with a React frontend and an ASP.NET Restful API backend) using the DDD principles. We also use our own Identity Provider (using IdentityServer4).

All IdP-related data is stored in its own seperate database (users, claims, resources,...).

Now there's this issue where we can't wrap our heads around:

Whenever a users logs onto our SaaS platform using our IdP, we want to store some of the user data (id, language, email & name) in our application database. This is because we want to ensure referential integrity between users and other domain entities.

Another reason to store this, is because we need to access users' languages from our domain (to send out emails etc).

So what we can do is read the users' claims and store these in our database. But next to that, whenever a users changes any of this data (lets say a users updates his language) in the IdP, we'd also need to update this data in our application database (since we want the users to receive emails in their set language).

I was thinking of creating a middleware that checks all UserClaims whenever a user performs an API call, but that would mean that we'd constantly have to make a db-request on every API call.

What is the best way to sync user data between the IdP and another database without having to do it manually?

My company is developing a SaaS service to store events and provide analytics through dashboards.

Since we won't have deletes or updates, the idea is to create a columnar-based, OLAP architecture to benefit from compression and latency it provides, and PostgreSQL Citus is one platform we intend to evaluate.

The overall architecture is pretty standard: an API will receive the events and then store them on Kafka in JSON format. Then, those events will be sent to PostgreSQL. Some fields will be "jsonb" data type.

By reading the docs, the best practice is distribute tables by tenant id.

Just wanted to doucle-check a few things and would greatly appreciate someone's input:

1. Does the architecture described above make sense? Is there anything we should change or pay attention to?
2. Are there limitations in the number of nodes or shards that can be scaled out for this columnar approach?
3. Is GIN index supported? (I believe it is, since it's not listed in 'Limitations')

Thanks!

I am working on Saas based application where I am using Laravel cashier. By default, Laravel cashier is using stripe. I want to use Razorpay instead of the stripe. Is it possible to achieve this in Laravel cashier? If Yes, Please let me know how?

I installed a camunda from the tutorial https://github.com/berndruecker/camunda-on-pcf and got it up and running

1. at localhost (http://localhost:8080/app/cockpit/default/#/dashboard)
2. on our PCF (https://our-private-pcf/app/cockpit/default/#/dashboard)

Then a made a BPMN model via Camunda modeler.

Question 1: Do i choose BPMN Diagram for "Camunda Platform" or for "Camunda Cloud"?

Question 2: Which value do I have to enter for "REST Endpoint" (Platform) or "Contact Point" (Cloud Self Managed) or "Cluster URL" (Cloud SaaS)?

I tried a lot of combinations of a) localhost oder Cloud URL and b) context root "/engine-rest/" or "/API/" or "/APP/" and so on but none of them works.

Thanks for your thoughts, Regards