Thanks for the info :) On Saturday, 5 September 2020 at 22:43:47 UTC+5:30 Matt Mansour wrote:
> As Ken mentioned infrastructure is not specific to Mezzanine. > > Scaling is based the level growth you're experiencing. > > You don't want to build your initial Mezzanine infrastructure for the > million users you don't have yet, nor the engineering team you don't have > yet. > > I start out mezzanine projects on AWS: using an EC2 instance for the app, > an RDS instance for the database, an elasticache instance for the caching > layer, and S3 / cloudfront for file storage. > > That approach is almost over optimization for something brand new. But it > also can handle the pleasant surprise of your app gaining traction. > > Once your app gets to a certain point the infrastructure needs to change. > There is also DevOps if you plan on having an engineering team iterate on > your code base. > > Just get your App up and running to test your hypothsis first (that people > will actually visit your project) > > That said, if you're at a funded startup, or you have a large tribe on > deck and ready for your app, check out some dev ops and > infrastructure courses on Udemy and use Mezzanine with it. > > On Sat, Sep 5, 2020 at 4:26 AM nitish kumar <vulli...@gmail.com> wrote: > >> Hi Ken, >> >> I am just trying to pick a topic where I can contribute to Mezzanine. >> I can see all gallery content is stored in files which will be a problem >> if you want to scale horizontally. >> so checking if already there is a way to scale if not will try to do >> something. >> >> Thanks, >> Nitish >> >> On Sat, Sep 5, 2020 at 4:23 PM Ken Bolton <kenb...@gmail.com> wrote: >> >>> On Sat, Sep 5, 2020 at 6:48 AM nitish kumar <vulli...@gmail.com> wrote: >>> >>>> If anyone already able to scale please let me know. >>>> >>> >>> What have you tried? Where is your bottleneck? >>> >>> Mezzanine is (and remains) just a Django app, so your strategies for >>> scaling will not be specific to Mezzanine. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Mezzanine Users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/mezzanine-users/n5zr8XJwTos/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> mezzanine-use...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/mezzanine-users/CAN7ek0NE%2BEL3rjaJ2UcVaoZ7b8PUocG3h9mGHSus5BozcoukUQ%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/mezzanine-users/CAN7ek0NE%2BEL3rjaJ2UcVaoZ7b8PUocG3h9mGHSus5BozcoukUQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> > You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mezzanine-use...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mezzanine-users/CAChxUc-RNKwiqsXbfng5bWW3RWHjyaP-jf%3Dw3-MtQTtrVyHRrg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/mezzanine-users/CAChxUc-RNKwiqsXbfng5bWW3RWHjyaP-jf%3Dw3-MtQTtrVyHRrg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mezzanine-users/7ff08f79-c36c-47eb-85a2-b9eb84d79fbcn%40googlegroups.com.
