Hi Google, I am looking forward to your answer ... I described my use cases and what I want, do you need anything else? Any other information? I will appreciate your advice or tips.
Thanks for response Jaromir út 19. 1. 2021 v 21:23 odesílatel behavin behavin <[email protected]> napsal: > Hi Elliott, > I appreciate you answering me, thanks for links I started to reading it > from begining. I have also deployed my springboot application to Google App > Engine Standard . It works but I have some problems with that. > > My use case: > - I would like use "platform-as-a-service", where I deploy my springboot > app (jar or war) and let application running for long time. > - My app is connected to google cloud SQL (mysql8). > - I would like use advantage of simple maintain and scaling > (automatically create more instances if it will be necessary). > - I would like use a similar product like Elasticbeanstalk on AWS, (using > Apache Tomcat 9.x , springboot is familiar with it) but from Google Cloud. > - My application has cca 100MB (with libraries). > - In first phase I expect just only hundreds or thousands requests per > whole day. > - I would like use CI/CD from gitlab. > > Now, after I deployed to Google App Engine Standard (runtime: java11, > instance_class: B2, manual_scaling: instances: 1 ) I have this problem: > - During or after the app start I noticed that server is several times > restarted. After cca 5 minutes it is stable and working normally. I am not > sure if Google App Engine Standard is suitable solution for me... > > Thanks for answer and have a nice day. > Jaromír > > > Dne úterý 19. ledna 2021 v 16:05:35 UTC+1 uživatel Elliott (Cloud Platform > Support) napsal: > >> Hello Jaromir, >> >> I understand that you would like some advice on running your Spring Boot >> application on Google Cloud Platform. There are a few ways you can do this. >> For example, you may use Google App Engine Standard or Google Google >> Kubernetes GKE, both having tutorials here >> <https://developers.google.com/learn/pathways/springboot-google-cloud>. >> >> To offer the best advice, what are your concerns specifically? Maybe >> after using the information from the links, you would be more sure. >> >> The community would recommend an environment but if you provide your use >> case, it will be easier. >> >> For example, for Google App Engine Standard, applications can be easy to >> create. Since this is managed, the app may be simple to maintain and scale >> depending on traffic and data. You don’t need to maintain a server. In >> theory, you upload your app and that’s it. >> >> >> On Monday, January 18, 2021 at 2:35:57 PM UTC-5 [email protected] wrote: >> >>> >>> Hi, >>> I have a Spring boot application that produce small public REST API. Is >>> written in Java11 and I would like to run it in Apache Tomcat 9.x . >>> >>> >>> Could you recommend me , which environment should I use on GCP? >>> >>> I started with App Engine (standard environment), but I am not sure if >>> it is suitable form java + spring application. >>> >>> I would like to run my app in 1 instance, later (if will be necessary ) >>> to scale in more instance. >>> >>> Thanks for advice. >>> Jaromir >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/0dcf815e-e2c9-44a8-a25b-a914dcf73179n%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/0dcf815e-e2c9-44a8-a25b-a914dcf73179n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAAEpCaUwkTBMrDHbLoM6mhzj9iQS98n%2B4hOQ6N682NPOitoCQw%40mail.gmail.com.
