i am creating a flat management software in PHP (codeigniter).
now client need to create different sub domains for different builders but should maintain only single database.
Related
I'm trying to create a multi-tenant application and which will be hosted in a single instance. To complete this application I need to implement a Redis cache system. I have two solutions for multi-tenant caching. They are,
I can prefix the keys with tenant name like tenant1:myKey etc
I can use different in-memory DB provided by Redis. I can store different tenant details in different DB. To fetch them connect with the respective DB.
If I go with the second option, is there any disadvantages/performance issue? and if you can suggest any other solutions please help me!!
Note: I don't want to use Redis clustering
I'm building a multi-tenant saas application using laravel 5.7 and vuejs. Whatever new client register the system will create new database for him as well all table migrations and seeding will be done via events.
But when super admin manage the application, how to load each client data to super admin panel, or let's say super admin want to make a announcement to al of his client, how to handle this in laravel so announcement data get synced to all database.
Maybe create a separate DB for SUPER-ADMIN, and that DB will be contains clients_table and other data needed to read/write data in clients-DB (data like client db name, user, password, for establish connection to his db etc.).
Alternatively - you can create special table `clients_announcments' in super-admin-db (or may be new db: common_clients_db) and use it for that (and read it from clients) - depends of how many clients you have and what efficency you need
If you create so "big" saas system with many DB, I also encourage you to hard separation between backend and frontend - this means laravel backend will only provide Restful API (NO html-css-js code - only pure php), and frotend client will be separate vue/angular/react project which will consume that API. Key words "micro-service architecture", "restful api"
Hello I am trying to build an application using Oracle ADF.
I have designed my database using Oracle Workbench have all the tables in the database already linked.( be it one to many or one to one mapping with the primary and foreignm keys.) i hope to include triggers too.
My problem is when i do all these links in workbench.
Will it automatically link the tables up using Association when i I load the tables as entities.
Will it also create views and view links too for me.
Or i should just create the tables in the database and do the associations and links in jdeveloper instead when i start working on the UI of my project.
If you use New - Business Tier - ADF Business Components - Business Components from Tables and go through the wizard pointint your tables in the database, JDeveloper should create Entities, link them with Associations, also create View Objects and link them with View Links based on your tables' foreign keys.
Triggers won't be reflected in the application.
An application permits admin users to upload CSV-files and save them as database tables.
The application uses Spring+JPA+Hibernate to access the database. How can I access the dynamically added new tables/entities to the system, without restarting or even recoding the system?
I would like to use EF 4.0 against Oracle. The challenge I have is that I have multiple databases (all with nearly identical schemas) for different clients. Is it possible to generate my CRUD layer once, and then point at the correct database at runtime based on user identity (or whatever criteria I need to supply)? I think I can handle the small differences between schemas by using POCO classes or just handling it in the partial classes, but I'm not sure how to handle directing to the correct database. Any Ideas?
The most simple solution is to create several named connection strings in your configuration file and then simply to create different instances of the same ObjectContext with different conection string parameter using a parameterized constructor.
Don't forget to delete the Schema attribute from your .edmx file (using XML Editor, for example).