Nueva publicación

查找

Artículo
· 30 mayo, 2025 Lectura de 8 min

VIP en Azure

Si estás ejecutando IRIS en una configuración en mirror para alta disponibilidad (HA) en Azure, la cuestión de proporcionar una Mirror VIP (Virtual IP) es relevante. La Virtual IP ofrece una forma para que los sistemas interactuen con IRIS utilizando una dirección IP. Incluso cuando ocurre un failover, los otros sistemas pueden reconectarse a la misma dirección IP y continuar trabajando.

El problema principal, cuando se despliega en Azure, es que una IRIS VIP tiene el requerimiento de que IRIS sea esencialmente un admin de red, según se indica en la documentación.

Para tener HA, los miembros en mirror de IRIS deben ser desplegados en diferentes zonas de disponibilidad (availability zones o AZ) en una subred (lo que es posible en Azure ya que las subredes pueden abarcar varias zonas). Una de las soluciones puede ser utilizar balanceadores de carga pero, por supuesto, suponen un coste extra, y también necesitarás administrarlos.

En este artículo, quiero proporcionar un modo de configurar una Mirror VIP sin la utilización de balanceadores de carga que se sugiere en la mayoría de las propouestas de arquitectruas de referencia para Azure.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Artículo
· 30 mayo, 2025 Lectura de 3 min

How to manage in a CI/CD pipeline an InterSystems API Manager configuration ?

Kong provides an open source configuration management tool (written in Go), called decK (which stands for declarative Kong)

  • Check that decK recognizes your Kong Gateway installation via deck gateway ping
deck gateway ping   
Successfully connected to Kong!
Kong version:  3.4.3.11
  • Export Kong Gateway configuration to a file named "kong.yaml" via deck gateway dump
deck gateway dump -o kong.yaml
  • After modifying the IP adcresses in kong.yaml file, show the differences via deck gateway diff
deck gateway diff kong.yaml

updating service test-iris  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "8fc9849d-9e61-402d-bcad-c3e611808892",
   "name": "test-iris",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } updating service uct  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "96ad587e-8921-4d6c-acb7-3f7f7a7cc072",
   "name": "uct",
   "path": "/api/uct/",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } Summary:
  Created: 0
  Updated: 2
  Deleted: 0
deck gateway sync kong.yaml

updating service uct  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "96ad587e-8921-4d6c-acb7-3f7f7a7cc072",
   "name": "uct",
   "path": "/api/uct/",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } updating service test-iris  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "8fc9849d-9e61-402d-bcad-c3e611808892",
   "name": "test-iris",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } Summary:
  Created: 0
  Updated: 2
  Deleted: 0
deck gateway dump --workspace workspace1
deck gateway sync workspace1.yaml --workspace workspace1

For more information :

https://docs.konghq.com/deck/get-started

https://docs.konghq.com/deck/reference/faq/

https://github.com/Kong/deck/blob/main/CHANGELOG.md/

1 Comentario
Comentarios (1)2
Inicie sesión o regístrese para continuar
Artículo
· 30 mayo, 2025 Lectura de 3 min

Comment gérer une configuration InterSystems API Manager dans un pipeline CI/CD ?

Kong fournit en open source un outil de gestion de ses configurations (écrit en Go), appelé decK (pour declarative Kong)

  • Vérifiez que decK reconnaît votre installation Kong Gateway via deck gateway ping
deck gateway ping   
Successfully connected to Kong!
Kong version:  3.4.3.11
  • Exporter la configuration de Kong Gateway dans un fichier "kong.yaml" via deck gateway dump
deck gateway dump -o kong.yaml
  • Après avoir modifié les adresses IP dans le fichier kong.yaml, afficher les différences via deck gateway diff
deck gateway diff kong.yaml

updating service test-iris  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "8fc9849d-9e61-402d-bcad-c3e611808892",
   "name": "test-iris",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } updating service uct  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "96ad587e-8921-4d6c-acb7-3f7f7a7cc072",
   "name": "uct",
   "path": "/api/uct/",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } Summary:
  Created: 0
  Updated: 2
  Deleted: 0
deck gateway sync kong.yaml

updating service uct  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "96ad587e-8921-4d6c-acb7-3f7f7a7cc072",
   "name": "uct",
   "path": "/api/uct/",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } updating service test-iris  {
   "connect_timeout": 60000,
   "enabled": true,
-  "host": "192.168.65.1",
+  "host": "172.24.156.176",
   "id": "8fc9849d-9e61-402d-bcad-c3e611808892",
   "name": "test-iris",
   "port": 9092,
   "protocol": "http",
   "read_timeout": 60000,
   "retries": 5,
   "write_timeout": 60000
 } Summary:
  Created: 0
  Updated: 2
  Deleted: 0
deck gateway dump --workspace workspace1
deck gateway sync workspace1.yaml --workspace workspace1

Pour plus d'informations :

https://docs.konghq.com/deck/get-started

https://docs.konghq.com/deck/reference/faq/

https://github.com/Kong/deck/blob/main/CHANGELOG.md/

Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 30 mayo, 2025

Office space for rent in bangalore

Bangalore, known as the Silicon Valley of India, is a hub for startups, tech giants, and global enterprises. With its ever-evolving infrastructure and vibrant business ecosystem, finding the right office space for rent in Bangalore can give your business the strategic advantage it needs. Whether you're a budding entrepreneur or an established corporation, the city offers premium commercial spaces with world-class amenities and flexible lease options.

Popular areas like Whitefield, Koramangala, and Electronic City stand out as prime locations for office rentals. Whitefield is renowned for its tech parks and seamless connectivity to major highways and metro stations. Koramangala offers a dynamic mix of coworking spaces and traditional offices, ideal for startups looking to scale. Electronic City, on the other hand, houses major IT firms and provides a more industrial, large-scale office setup with excellent infrastructure support.

Today’s commercial properties in Bangalore come equipped with premium amenities such as high-speed internet, 24/7 security, ample parking, modern interiors, and eco-friendly designs. Businesses can also benefit from flexible lease terms—monthly, quarterly, or long-term—designed to suit varying operational needs.

Finding the perfect office space for rent in Bangalore is now easier than ever with a variety of listings available online. Whether you're looking for a plug-and-play office, a shared workspace, or an entire floor for your team, there's a solution tailored to your goals.

Investing in the right office space in Bangalore not only enhances your brand image but also boosts productivity and employee satisfaction. Explore the best commercial spaces in Bangalore today and set your business on the path to success.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Comentarios
· 30 mayo, 2025

Exploring Cache Object Script: Tips, Tricks, and Best Practices

Hey everyone,

I'm diving deeper into Caché ObjectScript and would love to open a discussion around the most useful tips, tricks, and best practices you’ve learned or discovered while working with it.

Whether you're an experienced developer or just getting started, ObjectScript has its own set of quirks and powerful features—some well-documented, others hidden gems. I’m looking to compile a helpful set of ideas from the community.

Some areas I’m especially interested in:

  • 💡 Clever use of %INCLUDE, macros, and preprocessor directives
  • ⚙️ Best practices in class-based development using %Persistent, %SerialObject, and %Library classes
  • 🚀 Performance tips when dealing with globals, indices, and queries
  • 🔁 Techniques for clean and reusable method design, including ClassMethod vs Method
  • 🧪 Debugging tricks or useful utilities like %SYS.Debug, %SYSTEM.OBJ, or logging tools
  • 🔐 Security considerations when exposing methods (like using web services or REST endpoints)
  • 📊 Experience working with dynamic objects, JSON, and interoperability

I'd also love to hear about:

  • Your favorite hidden features
  • How you handle error trapping and logging
  • Any custom utilities or wrapper methods you've built that save time

Let’s build a thread that both beginners and advanced ObjectScript users can benefit from.

Looking forward to your insights!

3 comentarios
Comentarios (3)6
Inicie sesión o regístrese para continuar