Modernizing EnvTracker Migration to Multi‑Tenancy Architecture for Enhanced Scalability and Maintenance / Aimen Islam Keskas

Public ISBD Titre : Modernizing EnvTracker Migration to Multi‑Tenancy Architecture for Enhanced Scalability and Maintenance Type de document : document électronique Auteurs : Aimen Islam Keskas ; khaled Nasri, Directeur de thèse Editeur : Setif:UFA Année de publication : 2025 Importance : 1 vol (53 f .) Format : 29 cm Langues : Anglais (eng) Catégories : Thèses & Mémoires:Informatique Mots-clés : Modernizing EnvTracker Index. décimale : 004 Informatique Résumé : This dissertationpresentsthemodernizationofEnvTracker,aSoftware‑as‑a‑Service(SaaS)platform forenhancingtraceabilityandautomationinsoftwaredeliverypipelines,developedduringanintern‑ ship atAlgoro,aFrenchstart‑upbasedinClamart.Theprojectaddressescriticallimitationsinthe existingsystem,includinganoutdatedfrontendstack,monolithicbackendarchitecture,andlackof multi‑tenancysupport,whichhinderedscalabilityandcompetitivepositioninginthemodernsoft‑ wareindustry. The primaryobjectivewastotransformEnvTrackerintoascalable,multi‑tenantSaaSplatform throughstrategicarchitecturalmodernization.Keyinnovationsincludetheimplementationofa control/applicationplaneseparationarchitecture,singlesign‑on(SSO)integrationforenterprise clients,schema‑basedtenantisolationusingPostgreSQL,andcomprehensiveDevOpspractices encompassingcontainerization,InfrastructureasCode(IaC),andautomatedCI/CDpipelines. The methodologyinvolvedasystematicapproachtoSaaStransformation,beginningwitharchitec‑ turalredesignandfoundationaltechnologyselection,followedbythedevelopmentofacentralized controlplanefortenantmanagementandbillingintegration.Thefrontendwascompletelyrefactored using modernframeworks,whilethebackendwasrestructuredtosupportmulti‑tenantoperations with robustsecurityandaccesscontrolmechanisms. Significantprogresshasbeenachieved,withthecontrolplanefullyoperationalandmajoradvance‑ mentsinthetenant‑facingapplication.Theimplementationdemonstratessuccessfulintegrationof modern technologiesandarchitecturalprinciples,resultinginimprovedscalability,maintainability, and security.Theprojectprovidesvaluableinsightsintoreal‑worldSaaStransformationchallenges, including schema‑basedmulti‑tenancyimplementation,secureservicecommunication,andauto‑ matedinfrastructureprovisioning. While themigrationprocessremainsongoing,theestablishedfoundationsupportsfuturephasesof development,particularlyfulltenantenvironmentmigrationandproductionrollout. Note de contenu : Sommaire Introduction 5 1 ProblemStatement 6 1.1 MainBusinessActivitiesoftheCompany . ........................ 7 1.1.1 ProblemAddressedbyEnvTracker . ....................... 7 1.1.2 ExistingTechnicalSolution . ........................... 7 1.1.3 MarketPotential . ................................. 7 1.2 ArchitectureoftheExistingSystem . ........................... 8 1.3 PlatformLimitationsandGoalsforModernization . ................... 9 Conclusion . ........................................... 10 2 BackgroundonMulti‑tenancy 11 2.1 ModernSaaS . ....................................... 12 2.1.1 TheTraditionalSoftwareDeliveryModel . .................... 12 2.1.2 TheEvolutiontoSaaSandMulti‑Tenancy . .................... 13 2.2 ComponentsofMulti‑TenantArchitecture . ....................... 14 2.2.1 ControlPlane . ................................... 15 2.2.2 ApplicationPlane . ................................ 15 2.2.3 GrayArea . ..................................... 16 2.3 DeploymentModels . ................................... 17 2.3.1 UnderstandingSiloandPoolModels . ...................... 17 2.3.2 FullStackSiloedModel . ............................. 17 2.3.3 FullStackPooledModel . ............................. 18 2.3.4 MixedFullStackModel . .............................. 19 2.3.5 MixedResourceModel . .............................. 20 Conclusion . ........................................... 21 3 TechnicalFoundations 22 3.1 WebTechnologiesandTechniques . ........................... 23 3.2 DatabaseandStorage . .................................. 23 3.3 DevOpsandInfrastructure . ................................ 24 3.4 ThirdPartyTools . ..................................... 24 3.5 AccessControl . ...................................... 25 Conclusion . ........................................... 25 4 ProposedArchitectureandSolution 26 4.1 OverviewoftheNewArchitecture . ............................ 27 4.1.1 SeparationofConcerns . ............................. 27 4.1.2 Tier‑BasedDeploymentStrategy . ........................ 27 4.1.3 TenantRoutingandDomainManagement . ................... 28 4.2 ControlPlaneComponents . ............................... 28 4.2.1 CentralApplicationUsingSveltekit . ....................... 28 4.2.2 GlobalPostgres . .................................. 29 4.2.3 SaaSDashboard . ................................. 29 4.2.4 SelfOnboardingFlow . .............................. 29 4.2.5 InternalOnboardingforEnterpriseTier . ..................... 31 4.2.6 Billing . ....................................... 31 4.2.7 SyncingTenantInformation . ........................... 32 4.3 ApplicationPlaneComponents . ............................. 33 4.3.1 NewTenantApplication . ............................. 33 4.3.2 SpringWorker . .................................. 33 4.3.3 TenantAppandSpringWorkerCommunication . ................ 34 4.3.4 PostgresandProvisioning . ............................ 35 4.3.5 Authentication . .................................. 35 4.3.6 AuthorizationSystem . .............................. 36 Conclusion . ........................................... 37 5 DeploymentStrategy 38 5.1 ContainerizationStrategy . ................................ 39 5.1.1 ImplementationNotes . .............................. 39 5.2 InfrastructureasCode(IaC) . ............................... 39 5.2.1 DevelopmentEnvironment . ........................... 40 5.2.2 StagingandProductionEnvironments . ..................... 40 5.2.3 EnterpriseTenantDeployment . ......................... 41 5.3 ContinuousIntegrationandContinuousDeployment . ................. 41 5.3.1 DevelopmentWorkflow . ............................. 42 5.3.2 HotfixDeployment(DirecttoProduction) . ................... 42 5.3.3 Staging+Blue‑GreenDeployment . ....................... 42 5.3.4 EnterpriseDeploymentFlow . .......................... 42 5.4 MonitoringandObservabilityFoundations . ....................... 43 5.5 SecurityConsiderations . ................................. 43 5.5.1 ThreatModel . ................................... 43 5.5.2 Mitigations . .................................... 43 Conclusion . ........................................... 44 Conclusion 45 Appendix: InternshipReport 46 ProjectTimeline,ScopeEvolution,andTechnicalChallenges . ................ 46 Online Resources . ........................................ 49 Visuals . .............................................. 49 CentralApplicationVisuals: . ............................... 49 TenantApplicationVisuals: . ............................... 51 Côte titre : MAI/1022 Modernizing EnvTracker Migration to Multi‑Tenancy Architecture for Enhanced Scalability and Maintenance [document électronique] / Aimen Islam Keskas ; khaled Nasri, Directeur de thèse . - [S.l.] : Setif:UFA, 2025 . - 1 vol (53 f .) ; 29 cm. Langues : Anglais (eng) Catégories : Thèses & Mémoires:Informatique Mots-clés : Modernizing EnvTracker Index. décimale : 004 Informatique Résumé : This dissertationpresentsthemodernizationofEnvTracker,aSoftware‑as‑a‑Service(SaaS)platform forenhancingtraceabilityandautomationinsoftwaredeliverypipelines,developedduringanintern‑ ship atAlgoro,aFrenchstart‑upbasedinClamart.Theprojectaddressescriticallimitationsinthe existingsystem,includinganoutdatedfrontendstack,monolithicbackendarchitecture,andlackof multi‑tenancysupport,whichhinderedscalabilityandcompetitivepositioninginthemodernsoft‑ wareindustry. The primaryobjectivewastotransformEnvTrackerintoascalable,multi‑tenantSaaSplatform throughstrategicarchitecturalmodernization.Keyinnovationsincludetheimplementationofa control/applicationplaneseparationarchitecture,singlesign‑on(SSO)integrationforenterprise clients,schema‑basedtenantisolationusingPostgreSQL,andcomprehensiveDevOpspractices encompassingcontainerization,InfrastructureasCode(IaC),andautomatedCI/CDpipelines. The methodologyinvolvedasystematicapproachtoSaaStransformation,beginningwitharchitec‑ turalredesignandfoundationaltechnologyselection,followedbythedevelopmentofacentralized controlplanefortenantmanagementandbillingintegration.Thefrontendwascompletelyrefactored using modernframeworks,whilethebackendwasrestructuredtosupportmulti‑tenantoperations with robustsecurityandaccesscontrolmechanisms. Significantprogresshasbeenachieved,withthecontrolplanefullyoperationalandmajoradvance‑ mentsinthetenant‑facingapplication.Theimplementationdemonstratessuccessfulintegrationof modern technologiesandarchitecturalprinciples,resultinginimprovedscalability,maintainability, and security.Theprojectprovidesvaluableinsightsintoreal‑worldSaaStransformationchallenges, including schema‑basedmulti‑tenancyimplementation,secureservicecommunication,andauto‑ matedinfrastructureprovisioning. While themigrationprocessremainsongoing,theestablishedfoundationsupportsfuturephasesof development,particularlyfulltenantenvironmentmigrationandproductionrollout. Note de contenu : Sommaire Introduction 5 1 ProblemStatement 6 1.1 MainBusinessActivitiesoftheCompany . ........................ 7 1.1.1 ProblemAddressedbyEnvTracker . ....................... 7 1.1.2 ExistingTechnicalSolution . ........................... 7 1.1.3 MarketPotential . ................................. 7 1.2 ArchitectureoftheExistingSystem . ........................... 8 1.3 PlatformLimitationsandGoalsforModernization . ................... 9 Conclusion . ........................................... 10 2 BackgroundonMulti‑tenancy 11 2.1 ModernSaaS . ....................................... 12 2.1.1 TheTraditionalSoftwareDeliveryModel . .................... 12 2.1.2 TheEvolutiontoSaaSandMulti‑Tenancy . .................... 13 2.2 ComponentsofMulti‑TenantArchitecture . ....................... 14 2.2.1 ControlPlane . ................................... 15 2.2.2 ApplicationPlane . ................................ 15 2.2.3 GrayArea . ..................................... 16 2.3 DeploymentModels . ................................... 17 2.3.1 UnderstandingSiloandPoolModels . ...................... 17 2.3.2 FullStackSiloedModel . ............................. 17 2.3.3 FullStackPooledModel . ............................. 18 2.3.4 MixedFullStackModel . .............................. 19 2.3.5 MixedResourceModel . .............................. 20 Conclusion . ........................................... 21 3 TechnicalFoundations 22 3.1 WebTechnologiesandTechniques . ........................... 23 3.2 DatabaseandStorage . .................................. 23 3.3 DevOpsandInfrastructure . ................................ 24 3.4 ThirdPartyTools . ..................................... 24 3.5 AccessControl . ...................................... 25 Conclusion . ........................................... 25 4 ProposedArchitectureandSolution 26 4.1 OverviewoftheNewArchitecture . ............................ 27 4.1.1 SeparationofConcerns . ............................. 27 4.1.2 Tier‑BasedDeploymentStrategy . ........................ 27 4.1.3 TenantRoutingandDomainManagement . ................... 28 4.2 ControlPlaneComponents . ............................... 28 4.2.1 CentralApplicationUsingSveltekit . ....................... 28 4.2.2 GlobalPostgres . .................................. 29 4.2.3 SaaSDashboard . ................................. 29 4.2.4 SelfOnboardingFlow . .............................. 29 4.2.5 InternalOnboardingforEnterpriseTier . ..................... 31 4.2.6 Billing . ....................................... 31 4.2.7 SyncingTenantInformation . ........................... 32 4.3 ApplicationPlaneComponents . ............................. 33 4.3.1 NewTenantApplication . ............................. 33 4.3.2 SpringWorker . .................................. 33 4.3.3 TenantAppandSpringWorkerCommunication . ................ 34 4.3.4 PostgresandProvisioning . ............................ 35 4.3.5 Authentication . .................................. 35 4.3.6 AuthorizationSystem . .............................. 36 Conclusion . ........................................... 37 5 DeploymentStrategy 38 5.1 ContainerizationStrategy . ................................ 39 5.1.1 ImplementationNotes . .............................. 39 5.2 InfrastructureasCode(IaC) . ............................... 39 5.2.1 DevelopmentEnvironment . ........................... 40 5.2.2 StagingandProductionEnvironments . ..................... 40 5.2.3 EnterpriseTenantDeployment . ......................... 41 5.3 ContinuousIntegrationandContinuousDeployment . ................. 41 5.3.1 DevelopmentWorkflow . ............................. 42 5.3.2 HotfixDeployment(DirecttoProduction) . ................... 42 5.3.3 Staging+Blue‑GreenDeployment . ....................... 42 5.3.4 EnterpriseDeploymentFlow . .......................... 42 5.4 MonitoringandObservabilityFoundations . ....................... 43 5.5 SecurityConsiderations . ................................. 43 5.5.1 ThreatModel . ................................... 43 5.5.2 Mitigations . .................................... 43 Conclusion . ........................................... 44 Conclusion 45 Appendix: InternshipReport 46 ProjectTimeline,ScopeEvolution,andTechnicalChallenges . ................ 46 Online Resources . ........................................ 49 Visuals . .............................................. 49 CentralApplicationVisuals: . ............................... 49 TenantApplicationVisuals: . ............................... 51 Côte titre : MAI/1022

Exemplaires (1)

Code-barres	Cote	Support	Localisation	Section	Disponibilité
MAI/1022	MAI/1022	Mémoire	Bibliothèque des sciences	Anglais	Disponible Disponible

---

1 (1 - 1 / 1)