Hi Giannis I did some research about how to implement frontend and setting up monitoring using prometheus, have compiled all my findings into a doc which I am attaching with this mail.Please let me know your views on it. Thanks & Regards Sanskar Gupta On Sat, Mar 27, 2021 at 1:59 PM SANSKAR GUPTA <snskr95 [ at ] gmail [ dot ] com> wrote: > Hi Giannis > I have opened 2 issues in the cms repo, related to monitoring and > frontend, we can discuss about specific topic in the issue itself , will be > easy to track stuff. > > Thanks and regards > Sanskar Gupta > > > On Fri, Mar 26, 2021 at 3:29 PM Giannis E. Skitsas <iskitsas [ at ] gmail [ dot ] com> > wrote: > >> Hi Sanskar, >> >> Do you really need to implement those endpoints for monitoring? There are >> already solutions which we could integrate. Just take into account that we >> want the whole solution to be dockerized and be able to scale. We prefer to >> use Kubernetes, so ideally we want to use monitoring tools that fit well >> there (Splunk, NetData, Prometheus, OpenMetrics, DataDog etc). >> >> Regarding Kubernetes/Performance, yes we have used small testbeds to see >> how autoscaler works, having videos been served from the >> SastixCms-Kubernetes deployment. See this guide >> <https://medium.com/@iskitsas/autoscale-a-java-cms-app-with-kubernetes-the-microk8s-approach-from-docker-to-kubernetes-7c021f7d8333> >> for details. We have also used a dockerized approach for one of our >> customers, with 3 large AWS instances serving content for ~5000 registered >> users per daily basis. We have also parameterized the setup there a little >> bit, to include NGINX proxies, for better caching and delivering of static >> files. So, there are some tradeoffs you have to do when serving large >> throughputs, and adopt your architecture accordingly. For this GSOC we are >> ok to see something up to experiment level as a proof of concept. If you >> are already familiar with those, we are open to discuss any improvements on >> architecture level and support it with any new implementations. >> >> For any proposed enhancements, create github issues and we can take the >> discussion from there. >> >> Thanks, >> Giannis >> -- >> Ioannis Skitsas >> >> >> >> On Fri, Mar 26, 2021 at 3:57 PM SANSKAR GUPTA <snskr95 [ at ] gmail [ dot ] com> wrote: >> >>> Hi Giannis >>> For GSOC stories , I was thinking if we can start by implementing >>> necessary endpoints for disk usage , memory /cpu usage etc using websockets >>> as it should be real time if I understand the functionality right. >>> After that spring security can be integrated with creator and admin >>> roles.We can discuss possibility of having more roles though >>> I see you are using hazelcast for caching which according to me is a >>> reasonable choice for distributed caching considering its a CMS. >>> My doubts are: Has the performance of this app been tested on >>> kubernetes, if yes what was the number of running instances? >>> Also let me know if my plan to get started with backend enhancements >>> sounds fine.We can then discuss the react app. >>> >>> >>> Thanks and regards >>> Sanskar Gupta >>> Masters Student at KTH Royal Institute of Technology, Stockholm >>> >>> >>> On Fri, Mar 26, 2021 at 9:41 AM Giannis E. Skitsas <iskitsas [ at ] gmail [ dot ] com> >>> wrote: >>> >>>> Hi Sanskar, >>>> >>>> Thanks a lot for your feedback. We will review your PR. >>>> >>>> Regarding the project see here >>>> <https://ellak.gr/wiki/index.php?title=Google_Summer_of_Code_2021_proposed_ideas#Expected_Results> >>>> for the expected results. We are open to any recommendations. >>>> >>>> GraphQL and the other "Features in pipeline" you see in the README are >>>> not all required for GSOC. Specifically for GraphQL we wanted to have this >>>> feature because it is easier for an integrator to understand our APIs and >>>> data, and get exactly what you are asking for. You are free to implement >>>> any of them if you feel you can deliver them in the proposed timeline. >>>> >>>> Let me know if you need any other information. >>>> >>>> Best regards, >>>> Giannis >>>> >>>> -- >>>> Ioannis Skitsas >>>> >>>> >>>> >>>> On Thu, Mar 25, 2021 at 7:13 PM SANSKAR GUPTA <snskr95 [ at ] gmail [ dot ] com> >>>> wrote: >>>> >>>>> Hi Mentors >>>>> This is regarding the cms project. >>>>> First of all there was an issue in readme , the image url in sample >>>>> request body to run the createResource endpoint was not working (was >>>>> throwing 400) >>>>> So I created an issue and a pull request for the same , requesting you >>>>> to review it. >>>>> >>>>> Pull Request Link <https://github.com/sastix/cms/pull/10> >>>>> >>>>> Now regarding the project and possible enhancements about security, >>>>> scalability and monitoring,I feel the following tech stack will be super >>>>> beneficial and insanely fun to implement >>>>> >>>>> Frontend: Using material ui components to create a react dashboard >>>>> for executing role based endpoints. >>>>> >>>>> Security:Integrating spring security for resource access management >>>>> >>>>> Monitoring: Setting up a Grafana dashboard for constant monitoring API >>>>> health and performance in TPS >>>>> >>>>> Scaling: Running the pods in a kubernetes pod with in place CI/CD >>>>> pipeline , there will be no downtime during container lifecycle >>>>> For CI/CD I would say I had some good experiences with CircleCI. >>>>> >>>>> For Archive API , any Relational DB should do the job where we can >>>>> store meta data into separate columns or in a single string if redundancy >>>>> is the deciding factor >>>>> >>>>> Not sure about the use case of GraphQL >>>>> >>>>> Request you to provide your thoughts on my choice of tech stack ,also >>>>> request you to explain me the use case of graphQL in cms. >>>>> >>>>> Thanks and Regards >>>>> Sanskar Gupta >>>>> Masters Student at KTH Royal Institute of Technology, Stockholm >>>>> >>>>> >>>>> >>>>> ---- >>>>> Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και >>>>> συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του >>>>> Google Summer of Code - A discussion list for student developers and >>>>> mentors of Google Summer of Code projects., >>>>> https://lists.ellak.gr/gsoc-developers/listinfo.html >>>>> Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. >>>>> ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr>. >>>>> >>>>
Attachment:
cms.pdf
Description: Adobe PDF document
---- Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του Google Summer of Code - A discussion list for student developers and mentors of Google Summer of Code projects., https://lists.ellak.gr/gsoc-developers/listinfo.html Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr>.