Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #39667
| From | Arne Vajhøj <arne@vajhoej.dk> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Going from java monolith to microservice |
| Date | 2021-01-21 19:02 -0500 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <rud4m0$o0d$1@gioia.aioe.org> (permalink) |
| References | <a3d61fad-4b76-4383-95d8-34af8a32022cn@googlegroups.com> <rtvi1c$1f3s$1@gioia.aioe.org> <7af929c0-ebc2-4b05-b0fe-38f7a70af528n@googlegroups.com> |
On 1/17/2021 8:08 AM, mike wrote: > The different modules are normally delivered as mononlith ( xzy.jar) since it is more convenient. > Some can work standalone ( like the lowest layer). > Then users ( intendend category is NETCONF device testers) can access what > ever layers the like: > > High level: > > NetconfClient client = NetconfClientBuilder.setConnectionTimeout(10).usePrettyPrint(true).build(); > client.create(); > > Low level: > > NetconfHandler netconf = NetconfHandler.createSshTransport(); > netconf.connection(String host,int port); > netconf.editConfig(Sting config,String target); > netconf.disconnect(); > > So as you can see there is no webservice used today. I guess I was not clear in my first description. Is an API that testers can use create their own test code for the NETCONF enabled device. > > The problem we have today it that there are many public classes that should not actually be used by testers. However we cannot change access since other dependent modules need these classes. > > I thought we could hide them using a microservice and also make it more clear for testers what can be accessed. I realize testers can not write code then ( as above shows) but instead create urls with parameters. > > So,after discussing with you guys, I realize that my real problem is to create a public API for each module > that is clear and consise for users to work with at any level, approx 5 levels. Top level has dependencies to lower levels ( chained). > > High level > ...... > Low level > > I guess a microservice will not solve this. Maybe I should not even think microservices. Is there a nother way to solve my problem. Can I do some preparation work in java 8 to move over to java 12 when it is time? Yep. It sounds like you need the new Java module system not micro-services. The new Java module system is a pretty good tool for hiding "internal public" classes. Arne
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
Going from java monolith to microservice mike <mikaelpetterson@hotmail.com> - 2021-01-16 06:29 -0800
Re: Going from java monolith to microservice Graeme Geldenhuys <graemeg@example.net> - 2021-01-16 16:16 +0000
Re: Going from java monolith to microservice mike <mikaelpetterson@hotmail.com> - 2021-01-16 08:44 -0800
Re: Going from java monolith to microservice Arne Vajhøj <arne@vajhoej.dk> - 2021-01-16 15:24 -0500
Re: Going from java monolith to microservice mike <mikaelpetterson@hotmail.com> - 2021-01-17 05:08 -0800
Re: Going from java monolith to microservice Graeme Geldenhuys <graemeg@example.net> - 2021-01-17 16:32 +0000
Re: Going from java monolith to microservice Arne Vajhøj <arne@vajhoej.dk> - 2021-01-21 19:02 -0500
csiph-web