rsrini7

* **Titans** are a new Transformer architecture with RNN memory.
* **RNNs** have limitations like vanishing gradients, limited memory, and sequential dependency.
* **Titans** address these limitations by combining RNNs and Transformers.
* **Addressing RNN Limitations:** Titans aim to overcome the shortcomings of Recurrent Neural Networks (RNNs), such as:
    * **Vanishing/Exploding Gradients:** Difficulty in training deep RNNs due to unstable gradient flow.
    * **Limited Memory:** RNNs struggle to capture and retain information over long sequences.
    * **Sequential Computation:** Processing information sequentially limits parallel processing capabilities.

* **Key Innovation: Neural Long-Term Memory:** 
    * Titans incorporate a dedicated neural module for long-term memory.

rsrini7

https://marketplace.visualstudio.com/items?itemName=liviuschera.noctis

rsrini7

mongodb

time series

Copped Collection -> fixed and retrieve insertion order, high throughput

Use Custom Collection -> rules for string comp letter case and assent marks 

Clustered Collection -> stores ordered by used defined cluster key

rsrini7

https://betterprogramming.pub/tracing-in-spring-boot-3-webflux-d432d0c78d3e

logging.pattern.level: "trace_id=%mdc{traceId} span_id=%mdc{spanId} trace_flags=%mdc{traceFlags} %p"

https://spring.academy/guides/microservices-observability-reactive-spring-boot-3
----------------

https://azizulhaq-ananto.medium.com/how-to-handle-logs-and-tracing-in-spring-webflux-and-microservices-a0b45adc4610

@Component

rsrini7

cmd -cur_console:n
powershell -cur_console:s1TVn
bash -cur_console:s1THn

rsrini7

https://www.dynatrace.com/news/blog/distributed-tracing-with-w3c-trace-context-for-improved-end-to-end-visibility/

https://engineering.dynatrace.com/open-source/standards/w3c-trace-context/

https://aloisreitbauer.medium.com/trace-context-and-the-road-toward-trace-tool-interoperability-d4d56932369c

https://stackoverflow.com/questions/76620276/use-both-b3-and-w3c-trace-formats-in-trace-propagation-between-spring-boot-2-3

rsrini7

java -jar wiremock-jre8-standalone-2.35.jar --port 9999

   ls -> __files and mappings folders 

wiremock recorder ->

	localhost:9999/__admin/recorder/
	

rsrini7

AWS CloudWatch
├── Metrics
│   ├── Custom Metrics
│   ├── EC2 Metrics
│   ├── RDS Metrics
│   ├── ELB Metrics
│   ├── Lambda Metrics
│   └── S3 Metrics
├── Alarms
│   ├── Actions

rsrini7

To use the Spring Actuator loggers endpoint in a traditional Spring application (i.e., one that does not use Spring Boot), you will need to do the following:

Add the spring-actuator dependency to your application.
Enable the loggers endpoint by adding the management.endpoint.loggers.enabled property to your application.properties file and setting it to true.
Configure the LoggersMvcEndpoint bean in your application context. This can be done by creating a configuration class that implements the ManagementConfigurer interface and overrides the configure method.
For example:

Copy code
@Configuration
public class ManagementConfig implements ManagementConfigurer {

rsrini7

We use a Socket Attaching Connector, which is enabled by default when the dt_socket transport is configured and the VM is running in the server debugging mode.

#Java Env Variable (Append $JAVA_OPTS or %JAVA_OPTS% if required)
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005"

#For Java 9 or above
Since Java 9.0 JDWP supports only local connections by default, add*:<port> to listen all interfaces
java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 <AppJar>

#For java 1.5 to 1.8: