{"id":79987,"date":"2020-05-02T01:42:42","date_gmt":"2020-05-01T23:42:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-quarkus-obedinyaet-microprofile-i-spring"},"modified":"2020-05-02T01:42:42","modified_gmt":"2020-05-01T23:42:42","slug":"kak-quarkus-obedinyaet-microprofile-i-spring","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/kak-quarkus-obedinyaet-microprofile-i-spring","title":{"rendered":"Kako Quarkus povezuje MicroProfile in Spring","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Pozdravljeni vsi, to je tretji prispevek v seriji o Quarkusu!<\/p>\n

\"Kako
\n
\nPri razvijanju Java mikroservisov se pogosto smatra, da Eclipse MicroProfile<\/a><\/noindex> in Spring Boot<\/a><\/noindex> \u2013 to so lo\u010deni in neodvisni API-ji. Obi\u010dajno programerji uporabljajo tiste API-je, ki so jim znani, saj u\u010denje novih ogrodij in komponent za izvajanje zahteva veliko \u010dasa. Danes bomo poskusili poenostaviti usvajanje nekaterih priljubljenih MicroProfile API-jev za Spring razvijalce<\/a><\/noindex> in pokazali, kako hkrati uporabiti Spring API in nove uporabne mo\u017enosti. Quarkus<\/a><\/noindex>.
\n<\/a><\/noindex>
\n\u010ce nekoliko podrobneje, bomo najprej obravnavali podro\u010dje uporabe in podrobnosti o tem, kako Quarkus podpira Spring API-je, da bomo pokazali Spring razvijalcem, kako lahko uporabljajo MicroProfile API v svojem vsakdanjem delu. Potem bomo predstavili MicroProfile API-je, ki bodo koristni Spring razvijalcem pri ustvarjanju mikroservisov.<\/p>\n

Zakaj prav Quarkus? Prvi\u010d, to je live coding, torej samodejno ponovno nalaganje vseh sprememb v MicroProfile API-jih, Spring API-jih in drugih Java API-jih, kar se izvede z eno samo ukazom: mvn quarkus:dev. Drugi\u010d, obravnavamo na\u0161 primer<\/a><\/noindex> storitev Person (ta se sestavi iz Spring, MicroProfile in JPA API-jev v binarno datoteko z uporabo nativne slike GraalVM) se za\u017eene v samo 0,055 sekunde in zasede pribli\u017eno 90 MB pomnilnika (RSS) na kon\u010dni to\u010dki RESTful aplikacije. Njena kompilacija pa se izvede z eno samo ukazom: mvn package -Pnative.<\/p>\n

Ne bomo se poglabljali v podrobnosti MicroProfile, ampak se bomo trudili, da pomagamo Spring razvijalcem razumeti, kako uporabiti Spring API-je skupaj z MicroProfile API-ji v Quarkusu.<\/p>\n

Kontejnerji in Kubernetes<\/h3>\n

\nDa ne bi preobremenili tega \u010dlanka, bomo tukaj obravnavali le vi\u0161je ravni vidike podpore Kubernetes<\/a><\/noindex>, saj je to pomembno razumeti. Quarkus se pozicionira kot Java kup za Kubernetes, ki minimizira porabo pomnilnika in \u010das zagona Java aplikacij in storitev, hkrati pa pove\u010duje gostoto njihovega name\u0161\u010danja na gostitelju in zmanj\u0161uje skupne stro\u0161ke.<\/p>\n

Quarkus prav tako podpira samodejno generiranje<\/a><\/noindex> Kubernetes virov in ponuja navodila<\/a><\/noindex> za uvajanje na platformah Kubernetes in Red Hat OpenShift. Poleg tega Quarkus samodejno generira datoteke Dockerfile.jvm (JVM pakiranje) in Dockerfile.native (pakiranje nativne binarne slike), potrebne za ustvarjanje kontejnerjev.<\/p>\n

In conclusion, focusing on Kubernetes as the target deployment environment, Quarkus does not use Java frameworks in cases where similar functionality is implemented at the Kubernetes platform level itself. Table 1 presents a functional mapping of Kubernetes and typical Java frameworks used by Spring developers.<\/p>\n

Table 1. Functional mapping of Java frameworks and Kubernetes.<\/i><\/p>\n

Functionality
\nTraditional Spring Boot
\nKubernetes<\/p>\n

Service discovery
\nEureka
\nDNS<\/p>\n

Konfiguracija
\nSpring Cloud Config
\nConfig Maps \/ Secrets<\/p>\n

Porazdelitev obremenitve
\nRibbon (client-side)
\nService, Replication Controller (server-side)<\/p>\n

<\/p>\n

Compiling and running the example code<\/h3>\n

\nIn this article, we refer to the example project<\/a><\/noindex>, where the Spring and MicroProfile APIs are used together and even that very Java class. The code from this example can be compiled and run from the command line; see the README.md file for more details.<\/p>\n

Spring Framework APIs<\/h3>\n

<\/p>\n

Dependency Injection<\/h4>\n

\nQuarkus supports a wide range of Contexts and Dependency Injection (CDI) APIs<\/a><\/noindex> and Spring Dependency Injection (Spring DI) APIs. If you are working with MicroProfile, Java EE and Jakarta EE<\/a><\/noindex>, you are already well acquainted with CDI. On the other hand, Spring developers can use the Quarkus Extension for Spring DI API to ensure compatibility with Spring DI. Examples of using supported Spring DI APIs are provided in Table 2.<\/p>\n

V the project from our example<\/a><\/noindex> uses both CDI and Spring Dependency Injection. More information and examples on this topic can be found in the Quarkus guide called Spring DI Guide<\/a><\/noindex>.<\/p>\n

Table 2. Examples of using supported Spring DI APIs.<\/i><\/p>\n

Supported features of Spring DI
\nPrimeri<\/p>\n

Constructor Injection<\/p>\n

public PersonSpringController(\n   PersonSpringRepository personRepository,  \/\/ injected      \n   PersonSpringMPService personService) {    \/\/ injected\n      this.personRepository = personRepository;\n      this.personService = personService;\n}\n<\/code><\/pre>\n
Field Injection
\nAutowired<\/a><\/noindex>
\nVrednost<\/a><\/noindex><\/p>\n
@Autowired\n@RestClient\nSalutationRestClient salutationRestClient;\n\n@Value(\"${fallbackSalutation}\")\nString fallbackSalutation;\n<\/code><\/pre>\n
Bean<\/a><\/noindex>
\n@Configuration<\/p>\n
@Configuration\npublic class AppConfiguration {\n   @Bean(name = \"capitalizeFunction\")\n   public StringFunction capitalizer() {\n      return String::toUpperCase;\n   }\n}\n<\/code><\/pre>\n
Component<\/a><\/noindex><\/p>\n
@Component(\"noopFunction\")\npublic class NoOpSingleStringFunction implements StringFunction {\n   @Override\n   public String apply(String s) {\n      return s;\n   }\n}\n<\/code><\/pre>\n
Storitev<\/a><\/noindex><\/p>\n
@Service\npublic class MessageProducer {\n   @Value(\"${greeting.message}\")\n   String message;\n\n   public String getPrefix() {\n      return message;\n   }\n}\n<\/code><\/pre>\n
<\/p>\n
Web framework<\/h4>\n
\nUporabnikom MicroProfile bo v\u0161e\u010d, da Quarkus podpira JAX-RS, MicroProfile Rest Client, JSON-P in JSON-B kot osnovni model za spletno programiranje. Razvijalce v Springu bo razveselila nedavno dodana podpora Quarkusa za Spring Web API, zlasti za vmesnike, ki skrbijo za REST. Po analogiji s Spring DI je glavni cilj podpore Spring Web API omogo\u010diti razvijalcem Springa, da uporabljajo API vmesnike Spring Web skupaj z API vmesniki MicroProfile. Primeri uporabe podprtih Spring Web API so navedeni v tabeli 3, dodatne informacije in primeri pa so na voljo v vodniku Quarkus, ki nosi naziv Spring Web Guide<\/a><\/noindex>.<\/p>\n
Tabela 3. Primeri uporabe podprtih API vmesnikov Spring Web.<\/i><\/p>\n
Podprte funkcionalnosti Spring Web
\nPrimeri<\/p>\n
@RestController
\n@RequestMapping<\/p>\n
@RestController\n@RequestMapping(\"\/person\")\npublic class PersonSpringController {\n   ...\n   ...\n   ...\n}\n<\/code><\/pre>\n
@GetMapping
\n@PostMapping
\n@PutMapping
\n@DeleteMapping
\n@PatchMapping
\n@RequestParam
\n@RequestHeader
\n@MatrixVariable
\n@PathVariable
\n@CookieValue
\n@RequestBody
\n@ResponseStatus
\n@ExceptionHandler
\n@RestControllerAdvice (delno)<\/p>\n
@GetMapping(path = \"\/greet\/{id}\",\n   produces = \"text\/plain\")\n   public String greetPerson(\n   @PathVariable(name = \"id\") long id) {\n   ...\n   ...\n   ...\n}\n<\/code><\/pre>\n
<\/p>\n
Spring Data JPA<\/h4>\n
\nUporabnikom MicroProfile bo prav tako ustrezala podpora Quarkusa za JPA z uporabo Hibernate ORM. Za razvijalce Springa je dobra novica, da Quarkus podpira splo\u0161no sprejete anotacije in tipe Spring Data JPA. Primeri uporabe podprtih API vmesnikov Spring Data JPA so navedeni v tabeli 4.
\nV the project from our example<\/a><\/noindex> uporabljajo se API vmesniki Spring Data JPA, dodatne informacije pa so na voljo v vodniku Quarkus z naslovom Spring Data JPA Guide<\/a><\/noindex>.<\/p>\n
Tabela 4. Primeri uporabe podprtih API vmesnikov Spring Data JPA.<\/i><\/p>\n
Podprte funkcionalnosti Spring Data JPA
\nPrimeri<\/p>\n
CrudRepository<\/p>\n
public interface PersonRepository\n         extends JpaRepository,\n                 PersonFragment {\n   ...\n}\n<\/code><\/pre>\n
Repository
\nJpaRepository
\nPagingAndSortingRepository<\/p>\n
public class PersonRepository extends \n\n    Repository {\n\n    Person save(Person entity);\n\n    Optional findById(Person entity);\n}\n<\/code><\/pre>\n
Repository Fragments<\/p>\n
public interface PersonRepository\n         extends JpaRepository,\n                 PersonFragment {\n   ...\n}\n<\/code><\/pre>\n
Derived query methods<\/p>\n
public interface PersonRepository extends CrudRepository {\n\n    List findByName(String name);\n    \n    Person findByNameBySsn(String ssn);\n    \n    Optional \n       findByNameBySsnIgnoreCase(String ssn);\n\n    Boolean existsBookByYearOfBirthBetween(\n            Integer start, Integer end);\n}\n<\/code><\/pre>\n
User-defined queries<\/p>\n
public interface MovieRepository\n         extends CrudRepository {\n\n    Movie findFirstByOrderByDurationDesc();\n\n    @Query(\"select m from Movie m where m.rating = ?1\")\n    Iterator findByRating(String rating);\n\n    @Query(\"from Movie where title = ?1\")\n    Movie findByTitle(String title);\n}\n<\/code><\/pre>\n
<\/p>\n
API vmesniki MicroProfile<\/h3>\n
<\/p>\n
Odporna na napake (Fault tolerance)<\/h4>\n
\nKonstrukcije odpornosti na gre\u0161ke so zelo pomembne za prepre\u010devanje kaskadnih napak in za ustvarjanje zanesljivih mikroservisnih arhitektur. Razvijalci Spring \u017ee leta uporabljajo circuit-breakerje za odpornost na napake. Hystrix<\/a><\/noindex>. Hystrix pa \u017ee dolgo ni bil posodobljen, medtem ko se microProfile-ov Fault Tolerance trenutno aktivno razvija in ima \u017ee ve\u010d let izku\u0161enj z uporabami v produkciji. Zato se za pove\u010danje zanesljivosti storitev v Quarkusu priporo\u010da uporaba API vmesnikov MicroProfile Fault Tolerance, katerih primere uporabe najdete v tabeli 5. Dodatne informacije so na voljo v vodniku Quarkus. Vodnik za odpornost na napake<\/a><\/noindex>.<\/p>\n
Tabela 5. Primeri uporabe podprtih API vmesnikov MicroProfile Fault Tolerance.<\/i><\/p>\n
Funkcije MicroProfile Fault Tolerance
\nOpis
\nPrimeri<\/p>\n
@Asynchronous<\/p>\n
Izvajanje logike v lo\u010denem niti<\/p>\n
@Asynchronous\n@Retry\npublic Future getSalutation() {\n   ...\n   return future;\n}\n<\/code><\/pre>\n
@Bulkhead<\/p>\n
Omejevanje \u0161tevila hkratnih zahtevkov<\/p>\n
@Bulkhead(5)\npublic void fiveConcurrent() {\n   makeRemoteCall(); \/\/...\n}\n<\/code><\/pre>\n
@CircuitBreaker<\/p>\n
Pametno obvladovanje napak in obnova po napakah<\/p>\n
@CircuitBreaker(delay=500   \/\/ milliseconds\n   failureRatio = .75,\n   requestVolumeThreshold = 20,\n   successThreshold = 5)\n@Fallback(fallbackMethod = \"fallback\")\npublic String getSalutation() {\n   makeRemoteCall(); \/\/...\n}\n<\/code><\/pre>\n
@Fallback<\/p>\n
Klic alternativne logike v primeru napake<\/p>\n
@Timeout(500) \/\/ milliseconds\n@Fallback(fallbackMethod = \"fallback\")\npublic String getSalutation() {\n   makeRemoteCall(); \/\/...\n}\n\npublic String fallback() {\n   return \"hello\";\n}\n<\/code><\/pre>\n
Retry<\/a><\/noindex><\/p>\n
Ponovni poskus pri napaki zahtevka<\/p>\n
@Retry(maxRetries=3)\npublic String getSalutation() {\n   makeRemoteCall(); \/\/...\n}\n<\/code><\/pre>\n
Timeout<\/a><\/noindex><\/p>\n
Nadzor \u010dasa \u010dakanja pri napaki<\/p>\n
@Timeout(value = 500)   \/\/ milliseconds\n@Fallback(fallbackMethod = \"fallback\")\npublic String getSalutation() {\n   makeRemoteCall(); \/\/...\n}\n<\/code><\/pre>\n
<\/p>\n
Preverjanje storitev (Health Service)<\/h4>\n
\nPlatforme Kubernetes spremljajo delovanje kontejnerjev z uporabo posebnih storitev. Da bi spodnja platforma lahko spremljala storitve, razvijalci Spring obi\u010dajno uporabljajo prilagodljive HealthIndicator in Spring Boot Actuator. V Quarkusu to lahko storite z MicroProfile Health, ki privzeto izvaja nadzor \u017eivljenjske sposobnosti (liveness check), vendar jih lahko nastavite tudi na hkratno preverjanje poslu\u0161nosti in pripravljenosti (readiness). Primeri uporabe podprtih API MicroProfile Health so navedeni v tabeli 6, dodatne informacije pa so predstavljene v vodniku Quarkus. Vodnik za zdravje<\/a><\/noindex>.<\/p>\n
Tabela 6. Primeri uporabe podprtih API vmesnikov MicroProfile Health.<\/i><\/p>\n
Funkcije MicroProfile Health
\nOpis
\nPrimeri<\/p>\n
@Liveness<\/p>\n
Platforma izvede ponovno nalaganje okvarjenih kontejneriziranih aplikacij.
\nEndpoint:
\nhost:8080\/health\/live<\/p>\n
@Liveness\npublic class MyHC implements HealthCheck {\n  public HealthCheckResponse call() {\n\n   ...\n   return HealthCheckResponse\n     .named(\"myHCProbe\")\n     .status(ready ? true:false)\n     .withData(\"mydata\", data)\n     .build();  \n}\n<\/code><\/pre>\n
@Readiness<\/p>\n
Plattform ne bo usmerjala prometa na kontejnerizirane aplikacije, \u010de niso pripravljene
\nEndpoint:
\nhost:8080\/health\/ready<\/p>\n
@Readiness\npublic class MyHC implements HealthCheck {\n  public HealthCheckResponse call() {\n\n   ...\n   return HealthCheckResponse\n     .named(\"myHCProbe\")\n     .status(live ? true:false)\n     .withData(\"mydata\", data)\n     .build();  \n}\n<\/code><\/pre>\n
<\/p>\n
Metrike<\/h4>\n
\nAplikacije zagotavljajo metrike bodisi v operativne namene (za spremljanje KPI-jev zmogljivosti SLA) bodisi v neoperativne (poslovne KPI-jev SLA). Razvijalci v Springu zagotavljajo metrike prek Spring Boot Actuator in Micrometer. Quarkus uporablja MicroProfile Metrics za zagotavljanje osnovnih metrik (JVM in operacijski sistem), metrik dobavitelja (Quarkus) in metrik aplikacij. MicroProfile Metrics zahteva, da implementacija podpira izhodne formate JSON in OpenMetrics (Prometheus). Primeri uporabe MicroProfile Metrics API so prikazani v Tabeli 7.<\/p>\n
V the project from our example<\/a><\/noindex> MicroProfile Metrics se uporablja za zagotavljanje metrik aplikacij. Dodatne informacije lahko najdete v priro\u010dniku Quarkus Vodnik po metrikah<\/a><\/noindex>.<\/p>\n
Tabela 7. Primeri uporabe API-jev MicroProfile Metrics.<\/i><\/p>\n
Funkcije MicroProfile Metrics
\nOpis
\nPrimeri<\/p>\n
@Counted<\/p>\n
Ozna\u010duje \u0161tevilo, ki \u0161teje \u0161tevilo klicev annotiranega objekta<\/p>\n
@Counted(name = \"fallbackCounter\", \n  displayName = \"Fallback Counter\", \n  description = \"Fallback Counter\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
@ConcurrentGauge<\/p>\n
Ozna\u010duje gauge-senzor, ki \u0161teje \u0161tevilo hkratnih klicev annotiranega objekta<\/p>\n
@ConcurrentGuage(\n  name = \"fallbackConcurrentGauge\", \n  displayName=\"Fallback Concurrent\", \n  description=\"Fallback Concurrent\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
@Gauge<\/p>\n
Ozna\u010duje gauge-senzor, ki meri vrednost annotiranega objekta<\/p>\n
@Metered(name = \"FallbackGauge\",\n   displayName=\"Fallback Gauge\",\n   description=\"Fallback frequency\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
@Metered<\/p>\n
Ozna\u010duje meter-senzor, ki spremlja frekvenco klicev annotiranega objekta<\/p>\n
@Metered(name = \"MeteredFallback\",\n   displayName=\"Metered Fallback\",\n   description=\"Fallback frequency\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
Metrika<\/a><\/noindex><\/p>\n
Annotacija, ki vsebuje informacije o metapodatkih ob prejemu zahteve za dodajanje ali dokon\u010danje metrike<\/p>\n
@Metric\n@Metered(name = \"MeteredFallback\",\n   displayName=\"Metered Fallback\",\n   description=\"Fallback frequency\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
Merjeno<\/a><\/noindex><\/p>\n
Ozna\u010duje \u010dasomer, ki spremlja trajanje annotiranega objekta<\/p>\n
@Timed(name = \"TimedFallback\",\n   displayName=\"Timed Fallback\",\n   description=\"Fallback delay\")\npublic String salutationFallback() {\n   return fallbackSalutation;\n}\n<\/code><\/pre>\n
\nMerilne to\u010dke (Metrics Endpoints)<\/b><\/p>\n
Merila aplikacij localhost<\/a><\/noindex>:8080\/metrics\/application
\nOsnovna merila localhost<\/a><\/noindex>:8080\/metrics\/base
\nMerila dobavitelja localhost<\/a><\/noindex>:8080\/metrics\/vendor
\nVsa merila localhost<\/a><\/noindex>:8080\/metrics<\/p>\n
Rest-strank MicroProfile<\/h4>\n
\nMikroservisi pogosto nudijo RESTful kon\u010dne to\u010dke, za katere so potrebni ustrezni API-ji strank. Za delo s RESTful kon\u010dnimi to\u010dkami Spring razvijalci obi\u010dajno uporabljajo RestTemplate. Quarkus pa ponuja za ta namen API-\u010dke MicroProfile Rest Client, katerih primere uporabe najdete v tabeli 8.<\/p>\n
V the project from our example<\/a><\/noindex> Uporaba RESTful kon\u010dnih to\u010dk se izvaja s pomo\u010djo MicroProfile Rest Client. Dodatne informacije in primeri so na voljo v Quarkus priro\u010dniku. Priro\u010dnik o Rest Client<\/a><\/noindex>.<\/p>\n
Tabela 8. Primeri uporabe API-jev MicroProfile Rest Client.<\/i><\/p>\n
Funkcije MicroProfile Rest Client
\nOpis
\nPrimeri<\/p>\n
@RegisterRestClient<\/p>\n
Registrira tipizirani Java vmesnik kot REST klienta.<\/p>\n
@RegisterRestClient\n@Path(\"\/\")\npublic interface MyRestClient {\n    @GET\n    @Produces(MediaType.TEXT_PLAIN)\n    public String getSalutation();\n}\n<\/code><\/pre>\n
@RestClient<\/p>\n
Ozmarka vstavitve primerka tipiziranega vmesnika REST klienta.<\/p>\n
@Autowired \/\/ or @Inject\n@RestClient\nMyRestClient restClient;\n<\/code><\/pre>\n
Klic<\/p>\n
Kli\u010de REST kon\u010dno to\u010dko.<\/p>\n
System.out.println(\n   restClient.getSalutation());\n<\/code><\/pre>\n
mp-rest\/url<\/p>\n
Dolo\u010da REST kon\u010dno to\u010dko.<\/p>\n
application.properties:\norg.example.MyRestClient\/mp-rest\/url=\n   http:\/\/localhost:8081\/myendpoint\n<\/code><\/pre>\n
<\/p>\n
Zaklju\u010dki<\/h3>\n
\nV tem blogu, ki bo v prvi vrsti koristen za Spring razvijalce, bomo na kratko obravnavali, kako v Quarkusu uporabiti Spring API-je skupaj z MicroProfile API-ji za razvoj Java mikroservisov in njihovo kompilacijo v nativno binarno kodo, kar prihrani stotine megabajtov pomnilnika in se za\u017eene v nekaj milisekundah.<\/p>\n
Kot ste \u017ee razumeli, dodatne informacije o podpori Spring in MicroProfile API-jem ter \u0161tevilne druge koristne informacije najdete v Quarkus priro\u010dnikih<\/a><\/noindex>.
\n
Izvor: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442, \u0438 \u0441 \u0432\u0430\u043c\u0438 \u0442\u0440\u0435\u0442\u0438\u0439 \u043f\u043e\u0441\u0442 \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u0440\u043e Quarkus! \u041f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 Java-\u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0447\u0430\u0441\u0442\u043e \u0441\u0447\u0438\u0442\u0430\u0435\u0442\u0441\u044f, \u0447\u0442\u043e Eclipse MicroProfile \u0438 Spring Boot \u2013 \u044d\u0442\u043e \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0435 \u0438 \u043d\u0435\u0437\u0430\u0432\u0438\u0441\u0438\u043c\u044b\u0435 \u0434\u0440\u0443\u0433 \u043e\u0442 \u0434\u0440\u0443\u0433\u0430 API. \u041f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e, \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0441\u0442\u044b, \u043a\u0430\u043a \u043f\u0440\u0430\u0432\u0438\u043b\u043e, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u0442\u0435 API, \u043a \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043e\u043d\u0438 \u0443\u0436\u0435 \u043f\u0440\u0438\u0432\u044b\u043a\u043b\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u043d\u043e\u0432\u044b\u0445 \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a\u043e\u0432 \u0438 runtime-\u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u0432 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u043c\u043d\u043e\u0433\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":79988,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-79987","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Kako Quarkus zdru\u017euje MicroProfile in Spring | ProHoster","description":"Pozdravljeni vsi, to je tretji prispevek v seriji o Quarkusu!","canonical_url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/kak-quarkus-obedinyaet-microprofile-i-spring","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sl_SI","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0430\u043a Quarkus \u043e\u0431\u044a\u0435\u0434\u0438\u043d\u044f\u0435\u0442 MicroProfile \u0438 Spring | ProHoster","og:description":"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442, \u0438 \u0441 \u0432\u0430\u043c\u0438 \u0442\u0440\u0435\u0442\u0438\u0439 \u043f\u043e\u0441\u0442 \u0438\u0437 \u0441\u0435\u0440\u0438\u0438 \u043f\u0440\u043e Quarkus!","og:url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/kak-quarkus-obedinyaet-microprofile-i-spring","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-05-01T23:42:42+00:00","article:modified_time":"2020-05-01T23:42:42+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"79987","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 16:27:13","updated":"2022-09-30 14:08:43","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/79987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/comments?post=79987"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/79987\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media\/79988"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media?parent=79987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/categories?post=79987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/tags?post=79987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}