I have implemented a clustered environment with a GemFire cache in Spring, using cache-server and client-cache. How can I implement authentication or any kind of security between client and server in a clustered environment?
#Sonal-
Several different ways! Have a look at...
https://github.com/jxblum/contacts-application/blob/apache-geode/security-example/src/test/java/example/app/geode/security/GeodeSecurityIntegrationTests.java
While this is coded for Apache Geode, it applies equally to Pivotal GemFire 9.x (which is based on Apache Geode 1.0.0-incubating).
You can also read my Spring.io Blog Post, which specifically covered Security. While this pertained to Spring Data for Apache Geode, it equally applies in Spring Data GemFire 2.0.0, which is based on Pivotal GemFire 9.0.x.
Hope this helps!
-John
Related
Looking for caching layer sitting on top of postgres like Redis…
If we change anything in memory it should get updated to Postgres…open source out of box integration between in memory and postgres…
I believe we can do with apache ignite..can you please point me how to do it? or any other in memory solution with Postgres
What is difference between grid gain and apache ignite?
Yes, the desired behavior could be achieved with Apache Ignite. You need to use CacheStore for 3rd party databases. You can even generate an Apache Ignite configuration that can handle the matter by parsing your existing schema through a JDBC connection. GridGain Community Edition is a source-available fork of Apache Ignite maintained by GridGain Systems (original author of Apache Ignite).
Can some one help in providing steps for creating a datasource for mongodb in websphere
A recommended approach for using the MongoDB java driver in WebSphere Application Server Liberty is documented here:
https://openliberty.io/blog/2019/02/19/mongodb-with-open-liberty.html
If you are using traditional WebSphere Application Server rather than Liberty, the CDI aspect of the approach is all standard and will work there as well, however, the MicroProfile Config part would not be available.
I am a beginner in Spring mvc, Spring Boot and Spring Data JPA. I am trying to create Microservices using Spring Boot. I created a sample database CRUD operation as microservice in Spring Boot. Now I have A requirement that develop a microservice using Spring Cloud.
When I referring documentation seeing Spring tools for creating application in distributed environment. I am confused about why we are using Spring Cloud? And what is actually meant by Spring Cloud? Is there any relation with Spring mvc?
Spring Cloud is for developing some of the common patterns in distributed systems.
Spring Cloud provides tools for developers to quickly build some of the common patterns in distributed systems (e.g. configuration management, service discovery, circuit breakers, intelligent routing, micro-proxy, control bus, one-time tokens, global locks, leadership election, distributed sessions, cluster state)
Spring Cloud
For Spring Boot and Spring MVC, see this nice answer difference-between-spring-mvc-and-spring-boot
I am looking to implement ElastiCache(using memcached) for my spring application. From here I can see that this can be done using spring cloud aws, but I could not find proper steps for doing this anywhere. Can anyone please provide some example implementation or tutorials?
Take a look at Simple Spring Memcached (SSM) project. It provides integration with AWS Elasticache through custom annotations or Spring Cache Abstraction.
I know that Apache Camel is java open source framework and Jboss Fuse is ESB which act like container to bind camel into its container . However i need to know its differences in some more depth .
Any help will be appreciated .
In simplified terms, camel framework is the set of api's (java code) which are used in system integration projects whereas fuse is the server like tomcat where code is deployed.
"JBoss Fuse combines several technologies like core Enterprise Service Bus capabilities (based on Apache Camel, Apache CXF, Apache ActiveMQ), Apache Karaf and Fabric8 in a single integrated distribution."
Deploy applications utilizing some different configurations and technologies is one of many qualities in Jboss Fuse.
"Camel" as being a rule based routing & mediation engine which can be used inside a full blown ESB, a message broker or a web services smart client. Though if you want to, you could consider that Camel is a small, lightweight embeddable ESB since it can provide many of the common ESB services like smart routing, transformation, mediation, monitoring, orchestration etc.
We should also mention what Camel isn’t. Camel isn’t an enterprise service bus complete(ESB ), although some call Camel a lightweight ESB because of its support for routing, transformation, monitoring, orchestration, and so forth. Camel doesn’t have a container or a reliable message bus, but it can be deployed in one, such as Open-ESB or ServiceMix. For that reason, we prefer to call
Camel an integration framework rather than an ESB.