Question:
We will be implementing a client that has 100,000 SKUs and to avoid performance issues on the production database, we would like to set this up as a separate organization ID so that we can set it up on a separate database / same server instance. Could you provide us with guidance or documentation on how to set this up?
As a background, this is our AWS environment:
ElasticBeanstalk for Frontend and Backend
RDS MySQL Aurora
EC2 MongoDB
AWS MSK for Kafka
Answer:
Do inform Sir Jason that we have spoken through this before during the discussion and to recap the minute meeting as below:
Structure
approach
Approach 1: Same server multiple VMs
(Equal to different client in different database)
·
On
AWS, create different instances of RDS. 3 clients 3 instances. (MySQL). MongoDB
and Kafka can be shared.
·
Separated
org ID. – currently need new license key.
Approach 2: Clients in same database
·
Option
1: Same Org ID
·
Option
2: Different Org ID on same MySQL database
·
Different
schema on same MySQL database.
·
Consideration
if put on one server
o
Performance
consideration.
o
Maintenance
is more difficult.
o
Customization
complication
Separated
Server especially when:
- Highly automation warehouse –
normally install with others warehouses.
- Separated by Region, industry
(Same similar flow) when more clients.
Q &
A
- What
if the client contract did not allow us to merge their data into other
client data?
- How
to deal with maintenance if you have 20 clients in one database by which
operating 24 by 7?
- If we setup in different schema
of same database, benefit: (1) easier to update database by client (2)
good to performance / dead lock . But we still need down time when update
application.
- If we put all clients on same
schema and db, we still need down time from all clients.
- How
to keep the data of inactive clients? We have experience wherein after 8
months closure of account, they suddenly ask for reactivation of the
system where they could access the data. Our data retention period is only
1-3months. Just anticipating this kind of scenario wherein a restoration
is required.
- Setup different schema for
different clients. The data can be removed and backup by schema.
- How
to deal with client with more than 700k SKU involve? Do you practice to
reside it on same database? Or best to do it on different database
instance.
- Suggest different Schema of
approach 2.
- If too many clients or heavy
automaton, still suggest approach 1.
According to Sir Jason,
CSO mentioned that there are many ways of improving performance. They want to check what would be your recommended way to address the additional 100k SKUs in this new warehouse for the client without setting up a new database.
Regards
Noted Ms. Lelean.
Dear GA,
Do send this to Sir Jonel for signature. Once done, I will create the meeting link.
Thanks
Sure.
I will create a service order and sent it over to signature and once it is done, I will send the invitation to Sir Jonel to invite his team.
Regards
Hi Ms. Lelean,
Sir Jonel is not available on Sep 8, they're requesting if Sep 9 is available?
I already informed them regarding this concern I will get back to you once they have a response. Thank You.
Is 8th Sept 2022 (Thursday) - whole day session is good?
Regards
Yes, they agree.
According to Sir Jason Ngo,
He wants to proceed with the creation of a new organization ID in production.
Regards,
Mark
Inform Fast if they want to proceed with the creation of a new organization ID in production, there will be a SR of 8 hours. 4 hours to show how to do it and another 4 hours for support and question on the creation.
Have they agree to the above?
According to Sir Jason,
They need your assistance to provide the license.
They want to confirm what they need to provide and if they need separate app server or they can provision in the existing app server and database.
Regards,
Mark
I will revert this to customer.
Inform Fast if they want to proceed with the creation of a new organization ID in production, there will be a SR of 8 hours. 4 hours to show how to do it and another 4 hours for support and question on the creation.
We want to understand what is the need for FAST to do this. If it is purely for performance, there are many ways to do it and not with creation of new Organization ID. Unless there are functional flow differ from the original warehouse. Take note that this will require additional OJV - which is a new license and if there is issue with this organization ID, Flux needs to be able to proof that it happens in the original Organization ID and in the warehouse HLS installed.
If they approve the SR, we will proceed with the signature.
Regards
According to Sir Jason Ngo,
Thanks, let's proceed with the creation of a new organization ID in production. Please let us know the activities to prepare.
Regards,
Mark
yes, I already reverted to customer.
Revert back to customer:
We calculate the spec based on orderlines and not SKU. Ask them to advice us on that.
By using a separate organization ID - it will be different license. They will need to buy additional license.
We only provide spec recommendation pdf and not the guidance or solution on the new organization ID.