Hi Ron, No issues with what you want to do with Camel and Spring Boot. You don't even need a container to run the application in (though Tomcat is small, simple and reliable). Using direct, bean and seda mappings you can achieve pretty much any sort of routing you would need for your app. If you have complex or convoluted routing requirements then Camel is a great fit even if your app is small, it'll still be fast though. Also, for the simpler routing cases we have, I find Camel to be a nice to have as it makes the logic much easier to read/see in the code and it decouples the processing part from the routing part. We can also take parts out and put them back in to the application with just a config change to some endpoint values.
I'd actually be interested in how you get on as from what you're describing it looks like you'll be using Camel in a similar function as the infamous Spring WebFlow framework. Regards, Valdis -----Original Message----- From: Ron [mailto:roncecch...@comcast.net] Sent: 17 April 2019 00:09 To: users@camel.apache.org Subject: Re: Camel + Spring Boot as a backend? Thanks, Mark, and everyone. To be clear, I’ve already written a half dozen or so Spring Boot / Camel apps (using Maven archetypes in IntelliJ), and I love it. I just wanted to know if it be advisable to build on what I know to complete a simple, low-throughput, low-availability, Java backend. And if I had read past chapter 5, I would’ve seen that Claus already starts describing in chapter 7something like what I want... Thanks again. Ron ------ Original Message ------ From: Mark Nuttall To: users@camel.apache.org Sent: April 16, 2019 at 5:52 PM Subject: Re: Camel + Spring Boot as a backend? I use Spring Boot extensively with Camel. It is a perfect pair for what you are asking about. I have i running locally on servers and also in aws in EC2. Works great both ways. Start by going to http://scanmail.trustwave.com/?c=6600&d=peC23I0uT7iOSfANXIYKpkC6CRDPq5VgwkknK46Byw&s=33&u=http%3a%2f%2fstart%2espring%2eio and pick Camel and JDBC (or JPA,etc), or if you have IntelliJ or STS you can just use those to create a spring boot app. You will want to add "web" and actuator so you can monitor the health of you app. On Tue, Apr 16, 2019 at 11:34 AM Luiz Eduardo Valmont<valm...@alis-sol.com.br>wrote:>I use Spring Boot, Camel and Quartz on a symbiotic-ish application. There's>REST endpoints as well.>>On Tue, 16 Apr 2019, 11:54 Michael Joyner,>wrote:>>>I assume using Spring MVC for the front end. I think that you would be>>fine. Someone else will probably chime in from the project and confirm.>>>>On Tue, Apr 16, 2019 at 7:29 AM Ron Cecchini>>wrote:>>>>>Hi, all. If/when anyone has any time, I was hoping to get a few quick>>>opinions.>>>(and I do mean be brief; I don't want anyone wasting time on this.)>>>>>>*** Could Camel + Spring Boot *alone* be used to implement the Java>>>portion of>>>*** a simple backend for a low-throughput, non-realtime system that>>>doesn't need to scale?>>>>>>Backstory: I was thinking about the web site for my sons' little league>>(I>>>didn't create it),>>>and what I might do if I were to redo it totally from scratch without>>>using Wordpress, etc.>>>>>>This quickly morphed (away from baseball and) into what it would take>to>>>implement what>>>basically amounts to a simple inventory tracking system of sorts.>>>>>>And the picture I had in mind is something like. Imagine you are an>>>online business with:>>>>>>- 100 customers or offices (whatever - call them "sites")>>>>>>- Each "site" is going to place at most, on average, 1 order a day>>>where an "order" might be to ship goods to another site, request>goods>>>from another site,>>>or order goods from a vendor (whatever - the details of the "order">>>don't matter)>>>>>>- Each site now needs to be able to track the progress of its order>>(where>>>its good are)>>>>>>Basically, something like a poor man's Amazon or USPS/UPS/FedEx>tracking>>>system.>>>>>>Again, the system doesn't need to scale because there will never be>more>>>than 100-200 sites.>>>Sites will spend the majority of their time inactive; i.e. not placing>>>orders.>>>Each order is a simple movement of goods (shipping or>>procuring/receiving).>>>There are no real time demands to know exactly where goods are. (A>daily>>>update would suffice.)>>>>>>Since the concurrency needs seem to be negligible, I don't see a need>for>>>a JBoss app server,>>>or a distributed server farm, etc. I feel like Camel will already>handle>>>whatever concurrency>>>issues that may arise, and its ability to seamlessly integrate with so>>>many others means alot of>>>the work is already done for me.>>>>>>What are your thoughts on trying to implement the backend of this>simple>>>inventory system with>>>a pretty simple Spring Boot + Camel + RDMS application, hosted on a>beefy>>>server and not running>>>in an app server or Docker?>>>>>>Thanks.>>>>>>Ron>>>>>>>>>-->>Sincerely,>>Michael Joyner>>> Vhi Group DAC (Vhi) is a holding company for insurance and healthcare services, which include Vhi Healthcare DAC, Vhi Insurance DAC, Vhi Health Services DAC and Vhi Investments DAC. Vhi Healthcare DAC trading as Vhi Healthcare and Vhi Insurance DAC trading as Vhi Insurance are regulated by the Central Bank of Ireland. Vhi Healthcare is tied to Vhi Insurance DAC for health insurance in Ireland which is underwritten by Vhi Insurance DAC. Vhi Healthcare is tied to Zurich Life Assurance plc for Vhi Life Term Insurance and Vhi Mortgage Protection which are underwritten by Zurich Life Assurance plc. Vhi Healthcare is tied to Collinson Insurance Solutions Europe Limited for MultiTrip Travel Insurance and Vhi Dental Insurance which are underwritten by Great Lakes Insurance SE and for Vhi International Health Insurance which is underwritten by Collinson Insurance Europe Limited. For more information about the Vhi Group please go to: https://www.vhi.ie/about-vhi. Tá Vhi Group DAC (Vhi) ina chuideachta sealbhaíochta le haghaidh seirbhísí árachais agus seirbhísí cúram sláinte, lena n-áirítear Vhi Healthcare DAC, Vhi Insurance DAC, Vhi Health Services DAC agus Vhi Investments DAC. Déanann Banc Ceannais na hÉireann rialáil ar Vhi Healthcare DAC, ag trádáil dó mar Vhi Healthcare, agus ar Vhi Insurance DAC, ag trádáil dó mar Vhi Insurance. Tá Vhi Healthcare ceangailte le Vhi Insurance DAC le haghaidh árachas sláinte in Éirinn, rud atá frithgheallta ag Vhi Insurance DAC. Tá Vhi Healthcare ceangailte le Zurich Life Assurance plc le haghaidh Árachais Saoil de chuid Vhi agus Árachas Cosanta Morgáiste de chuid Vhi atá frithgheallta ag Zurich Life Assurance plc. Tá Vhi Healthcare ceangailte le Collinson Insurance Solutions Europe Limited le haghaidh Árachas Taistil Ilturais agus Árachas Fiaclóireachta de chuid Vhi atá frithgheallta ag Great Lakes Insurance SE agus le haghaidh Árachas Sláinte Idirnáisiúnta de chuid Vhi atá frithgheallta ag Collinson Insurance Europe Limited. Chun tuilleadh faisnéise a fháil faoi Ghrúpa Vhi, tabhair cuairt ar: https://www.vhi.ie/about-vhi. This e-mail and any files transmitted with it contain information which may be confidential and which may also be privileged and is intended solely for the use of the individual or entity to whom it is addressed. Unless you are the intended recipient you may not copy or use it, or disclose it to anyone else. Any opinions expressed are that of the individual and not necessarily that of the Vhi Group. If you have received this e-mail in error please notify the sender by return.
