# Handling multiple express applications

**URL:** <https://forum.serverless.com/t/handling-multiple-express-applications/17895>\
**Category:** Serverless Architectures\
**Tags:** aws, api-gateway\
**Created:** [November 16, 2022, 10:14pm UTC](https://forum.serverless.com/t/handling-multiple-express-applications/17895 "2022-11-16T22:14:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![renanbrando](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/renanbrando/32/7171_2.png) [@renanbrando](https://forum.serverless.com/u/renanbrando)\
**Post date:** [November 16, 2022, 10:14pm UTC](https://forum.serverless.com/t/handling-multiple-express-applications/17895/1 "2022-11-16T22:14:35Z")

</div>

I was wondering what is the best practice for deal with multiple express applications using only one api gateway. Is it considered a good practice to put an express application under different base paths such as:  
API 1 [my.api.com/service-1](http://my.api.com/service-1)  
API 2 [my.api.com/service-2](http://my.api.com/service-2)

under each base path service-1 and service-2 I could deploy an express application with its router set to /  
Is there any project boilerplate or doc I could follow to reach a best approach for a scalable application?

Thanks
