ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A concise architecture note for serving TensorFlow models with SavedModel and TensorFlow Serving: minimal design, trust boundaries, operational checks, failure modes and conditions that trigger a redesign.
A decision guide comparing TensorFlow SavedModel and TensorFlow Lite for edge inference, with constraints, trade‑offs, a conversion example, and validation steps.
I am designing a deployment pipeline where a tf.keras model containing several custom layers must be exported via model.save() in SavedModel format and later reloaded in a separate process, potentially by a team that does not have the original layer classes importable. Assume TensorFlow 2.x with eager execution. The documented contract is that custom layers
Custom Layer Serialization in TensorFlow Keras When utilizing tf.keras.models.load_model to restore a model containing custom layers or loss functions, TensorFlow requires a custom_objects dictionary to map serialized names back to their Python implementations. While this mechanism handles basic custom classes, consistency issues arise when models are transf
When a Keras model is exported with model.save() in TensorFlow 2.x, the resulting SavedModel directory may lack a concrete function under the serving_default signature key that TensorFlow Serving expects. The goal is to confirm that the exported model contains a signature with defined input names and shapes that match the production request format, especiall
keras
tensorflow